Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Included schema SDCResources.xsd
Namespace urn:ihe:qrph:sdc:2016
Properties
attribute form default unqualified
element form default qualified
version 3.0
Element ExtensionBaseType / Comment
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCBase_xsd.tmp#CommentType_val SDCBase_xsd.tmp#CommentType
Type CommentType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Comment" type="CommentType">
</xs:element>
Element ExtensionBaseType / Extension
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCBase_xsd.tmp#ExtensionType
Type ExtensionType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
ANY element from ANY namespace
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Extension" type="ExtensionType">
</xs:element>
Element ExtensionBaseType / Property
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PropertyType_propName SDCResources_xsd.tmp#PropertyType_propClass SDCResources_xsd.tmp#PropertyType_val SDCResources_xsd.tmp#PropertyType_TypedValue SDCResources_xsd.tmp#PropertyType
Type PropertyType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Property, TypedValue
Instance
<Property name="" order="" propClass="" propName="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <TypedValue name="" order="" styleClass="" type="">{0,1}</TypedValue>
</Property>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
propClass xs:NMTOKENS optional
NEW
propName xs:NMTOKEN required
NEW
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Property" type="PropertyType"/>
Element PropertyType / TypedValue
Namespace urn:ihe:qrph:sdc:2016
Annotations
Contains optional typed data.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType
Type DataTypes_SType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Instance
<TypedValue name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <anyType maxLength="" minLength="" name="" namespace="" order="" schema="" styleClass="" type="">{1,1}</anyType>
  <anyURI name="" order="" styleClass="" type="" val="">{1,1}</anyURI>
  <base64Binary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</base64Binary>
  <boolean name="" order="" styleClass="" type="" val="">{1,1}</boolean>
  <duration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</duration>
  <byte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</byte>
  <date name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</date>
  <dateTimeStamp name="" order="" styleClass="" type="" val="">{1,1}</dateTimeStamp>
  <decimal name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</decimal>
  <dateTime name="" order="" styleClass="" type="" val="">{1,1}</dateTime>
  <double mask="" name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</double>
  <float name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</float>
  <gDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gDay>
  <gMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonth>
  <gMonthDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonthDay>
  <gYear name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYear>
  <gYearMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYearMonth>
  <hexBinary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</hexBinary>
  <HTML name="" order="" styleClass="" type="">{1,1}</HTML>
  <int name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</int>
  <integer name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</integer>
  <long name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</long>
  <negativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</negativeInteger>
  <nonNegativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonNegativeInteger>
  <nonPositiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonPositiveInteger>
  <positiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</positiveInteger>
  <short name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</short>
  <string name="" order="" styleClass="" type="" val="">{1,1}</string>
  <time name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</time>
  <unsignedByte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedByte>
  <unsignedInt name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedInt>
  <unsignedLong name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedLong>
  <unsignedShort name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedShort>
  <XML name="" order="" schema="" styleClass="" type="">{1,1}</XML>
  <yearMonthDuration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</yearMonthDuration>
</TypedValue>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="TypedValue" type="DataTypes_SType">
  <xs:annotation>
    <xs:documentation>Contains optional typed data.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / anyType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyType_DEtype_minLength SDCDataTypes_xsd.tmp#anyType_DEtype_maxLength SDCDataTypes_xsd.tmp#anyType_DEtype_schema SDCDataTypes_xsd.tmp#anyType_DEtype_namespace SDCDataTypes_xsd.tmp#anyType_DEtype
Type anyType_DEtype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace
Attributes
QName Type Use Annotation
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
namespace xs:string optional
Namespace used in an XML Schema file, if any, used to constrain and validate the the content of this field.  This is similar to the use of namespaces with the xs:any element in XML Schemas.

See: http://www.w3.org/TR/xmlschema-0/#any
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
schema xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace
Source
<xs:element name="anyType" nillable="true" type="anyType_DEtype">
</xs:element>
Element DataTypes_SType / anyURI
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element name="anyURI" nillable="true" type="anyURI_Stype">
</xs:element>
Element DataTypes_SType / base64Binary
Namespace urn:ihe:qrph:sdc:2016
Annotations
**SDC may need a valid list of MIME types.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#base64Binary_Stype_mimeType SDCDataTypes_xsd.tmp#base64Binary_Stype_val SDCDataTypes_xsd.tmp#base64Binary_Stype
Type base64Binary_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mimeType xs:string optional
TBD: Must be a valid MIME type
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:base64Binary optional
Source
<xs:element name="base64Binary" nillable="true" type="base64Binary_Stype">
  <xs:annotation>
    <xs:documentation>**SDC may need a valid list of MIME types.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / boolean
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#boolean_Stype_val SDCDataTypes_xsd.tmp#boolean_Stype
Type boolean_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:boolean optional
Source
<xs:element name="boolean" nillable="true" type="boolean_Stype"/>
Element DataTypes_SType / duration
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

Duration Data Type The duration data type is used to specify a time
 interval. The time interval is specified in the following form:
 "PnYnMnDTnHnMnS" where: 
 P indicates the period (required) 
 nY indicates the number of years nM indicates the number of months 
 nD indicates the number of days T indicates the start of a time section
 (required if you are going to specify hours, minutes, or seconds) 
 nH indicates the number of hours nM indicates the number of minutes 
 nS indicates the number of seconds 
 
An element in your document might look like this: P5Y 
 The example above indicates a period of five years. 
Or it might look like this: P5Y2M10D. 
 The example above indicates a period of five years, two months, and 10 days. 
Or it might look like this: P5Y2M10DT15H. 
 The example above indicates a period of five years, two months, 10 days, and 15 hours. 
Or it might look like this: PT15H.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#duration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#duration_Stype
Type duration_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="duration" nillable="true" type="duration_Stype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form: "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / byte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#byte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#byte_Stype
Type byte_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:byte optional
Source
<xs:element name="byte" nillable="true" type="byte_Stype">
</xs:element>
Element DataTypes_SType / date
Namespace urn:ihe:qrph:sdc:2016
Annotations
**Does SDC need a list of valid patterns for all date/time types?
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#date_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#date_Stype
Type date_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:date optional
Source
<xs:element name="date" nillable="true" type="date_Stype">
  <xs:annotation>
    <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / dateTimeStamp
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype
Type dateTimeStamp_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_Stype">
  <xs:annotation>
    <xs:documentation>
    </xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / decimal
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#decimal_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#decimal_Stype
Type decimal_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:decimal optional
Source
<xs:element name="decimal" nillable="true" type="decimal_Stype">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / dateTime
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

DateTime Data Type The dateTime data type is used to specify a date
and a time. 
The dateTime is specified in the following form
"YYYY-MM-DDThh:mm:ss" where: 
YYYY indicates the year 
MM indicates the month 
DD indicates the day 
T indicates the start of the required time section 
hh indicates the hour mm indicates the minute 
ss indicates the second 
 
Time Zones To specify a time zone, you can either enter a time
in UTC time by adding a "Z" behind the time -
like this: 09:30:10Z 
or you can specify an offset from the UTC time 
by adding a positive or negative time behind the
time - like this: 09:30:10-06:00 or 09:30:10+06:00.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype
Type dateTimeStamp_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTime" nillable="true" type="dateTimeStamp_Stype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / double
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#double_Stype_val SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#double_Stype
Type double_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:double optional
Source
<xs:element name="double" nillable="true" type="double_Stype"/>
Element DataTypes_SType / float
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#float_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#float_Stype
Type float_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:float optional
Source
<xs:element name="float" nillable="true" type="float_Stype"/>
Element DataTypes_SType / gDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gDay_Stype
Type gDay_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gDay optional
Source
<xs:element name="gDay" nillable="true" type="gDay_Stype"/>
Element DataTypes_SType / gMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype
Type gMonth_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gMonth" nillable="true" type="gMonth_Stype"/>
Element DataTypes_SType / gMonthDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonthDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonthDay_Stype
Type gMonthDay_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonthDay optional
Source
<xs:element name="gMonthDay" nillable="true" type="gMonthDay_Stype"/>
Element DataTypes_SType / gYear
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gYear_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gYear_Stype
Type gYear_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gYear optional
Source
<xs:element name="gYear" nillable="true" type="gYear_Stype"/>
Element DataTypes_SType / gYearMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype
Type gMonth_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gYearMonth" nillable="true" type="gMonth_Stype"/>
Element DataTypes_SType / hexBinary
Namespace urn:ihe:qrph:sdc:2016
Annotations
**Does SDC need list of valid MIME types?
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#hexBinary_Stype_mimeType SDCDataTypes_xsd.tmp#hexBinary_Stype_val SDCDataTypes_xsd.tmp#hexBinary_Stype
Type hexBinary_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mimeType xs:string optional
TBD: Must be a valid MIME type - needs
enumeration
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:hexBinary optional
Source
<xs:element name="hexBinary" nillable="true" type="hexBinary_Stype">
  <xs:annotation>
    <xs:documentation>**Does SDC need list of valid MIME types?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / HTML
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#HTML_Stype
Type HTML_Stype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Source
<xs:element name="HTML" nillable="true" type="HTML_Stype"/>
Element DataTypes_SType / int
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#int_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#int_Stype
Type int_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:int optional
Source
<xs:element name="int" nillable="true" type="int_Stype">
</xs:element>
Element DataTypes_SType / integer
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#integer_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#integer_Stype
Type integer_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:integer optional
Source
<xs:element name="integer" nillable="true" type="integer_Stype">
</xs:element>
Element DataTypes_SType / long
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#long_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#long_Stype
Type long_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:long optional
Source
<xs:element name="long" nillable="true" type="long_Stype"/>
Element DataTypes_SType / negativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#negativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#negativeInteger_Stype
Type negativeInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:negativeInteger optional
Source
<xs:element name="negativeInteger" nillable="true" type="negativeInteger_Stype"/>
Element DataTypes_SType / nonNegativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype
Type nonNegativeInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonNegativeInteger optional
Source
<xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_Stype"/>
Element DataTypes_SType / nonPositiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype
Type nonPositiveInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonPositiveInteger optional
Source
<xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_Stype"/>
Element DataTypes_SType / positiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#positiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#positiveInteger_Stype
Type positiveInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:positiveInteger optional
Source
<xs:element name="positiveInteger" nillable="true" type="positiveInteger_Stype"/>
Element DataTypes_SType / short
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#short_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#short_Stype
Type short_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:short optional
Source
<xs:element name="short" nillable="true" type="short_Stype"/>
Element DataTypes_SType / string
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="string" nillable="true" type="string_Stype"/>
Element DataTypes_SType / time
Namespace urn:ihe:qrph:sdc:2016
Annotations
**possibly "HH:MM:SS:ms am/pm 12/24"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#time_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#time_Stype
Type time_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:time optional
Source
<xs:element name="time" nillable="true" type="time_Stype">
  <xs:annotation>
    <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_SType / unsignedByte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedByte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedByte_Stype
Type unsignedByte_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedByte optional
Source
<xs:element name="unsignedByte" nillable="true" type="unsignedByte_Stype"/>
Element DataTypes_SType / unsignedInt
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedInt_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedInt_Stype
Type unsignedInt_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedInt optional
Source
<xs:element name="unsignedInt" nillable="true" type="unsignedInt_Stype"/>
Element DataTypes_SType / unsignedLong
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedLong_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedLong_Stype
Type unsignedLong_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedLong optional
Source
<xs:element name="unsignedLong" nillable="true" type="unsignedLong_Stype"/>
Element DataTypes_SType / unsignedShort
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedShort_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedShort_Stype
Type unsignedShort_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedShort optional
Source
<xs:element name="unsignedShort" nillable="true" type="unsignedShort_Stype"/>
Element DataTypes_SType / XML
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#XML_Stype_schema SDCDataTypes_xsd.tmp#XML_Stype
Type XML_Stype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
schema xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="XML" nillable="true" type="XML_Stype"/>
Element DataTypes_SType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype
Type yearMonthDuration_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
Element CodingType / Code
Namespace urn:ihe:qrph:sdc:2016
Annotations
A standard code, or a local value from a custom coding system, that can be used to consistently identify, or provide a
standard value for, the coded item.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
maxOccurs 1
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" name="Code" nillable="true" type="string_Stype">
  <xs:annotation>
    <xs:documentation>A standard code, or a local value from a custom coding system, that can be used to consistently identify, or provide a standard value for, the coded item.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodingType / TypedValue
Namespace urn:ihe:qrph:sdc:2016
Annotations
Data type enumeration derived from W3C XML Schema. If
the code is derived from a local value system (e.g., numbered answer
choices such as clock positions, tumor grades, or clinical scoring
systems), then the data type of the local value may be specified
here. This may be important if the code value will need to me
manipulated mathematically.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType
Type DataTypes_SType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Instance
<TypedValue name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <anyType maxLength="" minLength="" name="" namespace="" order="" schema="" styleClass="" type="">{1,1}</anyType>
  <anyURI name="" order="" styleClass="" type="" val="">{1,1}</anyURI>
  <base64Binary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</base64Binary>
  <boolean name="" order="" styleClass="" type="" val="">{1,1}</boolean>
  <duration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</duration>
  <byte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</byte>
  <date name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</date>
  <dateTimeStamp name="" order="" styleClass="" type="" val="">{1,1}</dateTimeStamp>
  <decimal name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</decimal>
  <dateTime name="" order="" styleClass="" type="" val="">{1,1}</dateTime>
  <double mask="" name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</double>
  <float name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</float>
  <gDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gDay>
  <gMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonth>
  <gMonthDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonthDay>
  <gYear name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYear>
  <gYearMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYearMonth>
  <hexBinary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</hexBinary>
  <HTML name="" order="" styleClass="" type="">{1,1}</HTML>
  <int name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</int>
  <integer name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</integer>
  <long name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</long>
  <negativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</negativeInteger>
  <nonNegativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonNegativeInteger>
  <nonPositiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonPositiveInteger>
  <positiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</positiveInteger>
  <short name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</short>
  <string name="" order="" styleClass="" type="" val="">{1,1}</string>
  <time name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</time>
  <unsignedByte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedByte>
  <unsignedInt name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedInt>
  <unsignedLong name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedLong>
  <unsignedShort name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedShort>
  <XML name="" order="" schema="" styleClass="" type="">{1,1}</XML>
  <yearMonthDuration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</yearMonthDuration>
</TypedValue>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="TypedValue" type="DataTypes_SType">
  <xs:annotation>
    <xs:documentation>Data type enumeration derived from W3C XML Schema. If the code is derived from a local value system (e.g., numbered answer choices such as clock positions, tumor grades, or clinical scoring systems), then the data type of the local value may be specified here. This may be important if the code value will need to me manipulated mathematically.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodingType / CodeText
Namespace urn:ihe:qrph:sdc:2016
Annotations
The human readable text that accompanies the assigned code and represents the code's precise meaning (semantics) or
usage.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#RichTextType_val SDCResources_xsd.tmp#RichTextType_RichText SDCResources_xsd.tmp#RichTextType
Type RichTextType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, Extension, Property, RichText
Instance
<CodeText name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <RichText name="" order="" styleClass="" type="">{1,1}</RichText>
</CodeText>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element maxOccurs="1" minOccurs="0" name="CodeText" type="RichTextType">
  <xs:annotation>
    <xs:documentation>The human readable text that accompanies the assigned code and represents the code's precise meaning (semantics) or usage.</xs:documentation>
  </xs:annotation>
</xs:element>
Element RichTextType / RichText
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#HTML_Stype
Type HTML_Stype
Type hierarchy
Properties
content complex
Model
ANY element from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Source
<xs:element form="qualified" name="RichText" type="HTML_Stype"/>
Element CodingType / CodeMatch
Namespace urn:ihe:qrph:sdc:2016
Annotations
Degree of match between the mapped item and the assigned code - @codeMatchType holds an entry from an enumerated
list of match types.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#CodeMatchType_codeMatchEnum SDCResources_xsd.tmp#CodeMatchType_CodingMatchComment SDCResources_xsd.tmp#CodeMatchType
Type CodeMatchType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children CodingMatchComment
Instance
<CodeMatch codeMatchEnum="Exact Code Match" name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <CodingMatchComment name="" order="" styleClass="" type="" val="">{0,1}</CodingMatchComment>
</CodeMatch>
Attributes
QName Type Default Use Annotation
codeMatchEnum restriction of xs:string Exact Code Match optional
The degree of match between the coded item and the assigned code.
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="CodeMatch" minOccurs="0" type="CodeMatchType">
  <xs:annotation>
    <xs:documentation>Degree of match between the mapped item and the assigned code - @codeMatchType holds an entry from an enumerated list of match types.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodeMatchType / CodingMatchComment
Namespace urn:ihe:qrph:sdc:2016
Annotations
Comment about the degree of match between the mapped item and the assigned
code.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="CodingMatchComment" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Comment about the degree of match between the mapped item and the assigned code.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodingType / CodeSystem
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#CodeSystemType_CodeSystemName SDCResources_xsd.tmp#CodeSystemType_ReleaseDate SDCResources_xsd.tmp#CodeSystemType_Version SDCResources_xsd.tmp#CodeSystemType_OID SDCResources_xsd.tmp#CodeSystemType_CodeSystemURI SDCResources_xsd.tmp#CodeSystemType
Type CodeSystemType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children CodeSystemName, CodeSystemURI, Comment, Extension, OID, Property, ReleaseDate, Version
Instance
<CodeSystem name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <CodeSystemName name="" order="" styleClass="" type="" val="">{1,1}</CodeSystemName>
  <ReleaseDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</ReleaseDate>
  <Version name="" order="" styleClass="" type="" val="">{0,1}</Version>
  <OID name="" order="" styleClass="" type="" val="">{0,1}</OID>
  <CodeSystemURI name="" order="" styleClass="" type="" val="">{0,1}</CodeSystemURI>
</CodeSystem>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="CodeSystem" type="CodeSystemType" minOccurs="0">
</xs:element>
Element CodeSystemType / CodeSystemName
Namespace urn:ihe:qrph:sdc:2016
Annotations
The name of the coding system, as recommended by the
coding system curators, or as recommended by the agency that creates
standards for the code map in use.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="CodeSystemName" type="string_Stype">
  <xs:annotation>
    <xs:documentation>The name of the coding system, as recommended by the coding system curators, or as recommended by the agency that creates standards for the code map in use.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodeSystemType / ReleaseDate
Namespace urn:ihe:qrph:sdc:2016
Annotations
The day that the selected version of the coding system was released for general use by the coding system curators.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="ReleaseDate" type="dateTime_Stype">
  <xs:annotation>
    <xs:documentation>The day that the selected version of the coding system was released for general use by the coding system curators.</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodeSystemType / Version
Namespace urn:ihe:qrph:sdc:2016
Annotations
Version of the coding system, using the version format defined by the coding system
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Version" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Version of the coding system, using the version format defined by the coding system</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodeSystemType / OID
Namespace urn:ihe:qrph:sdc:2016
Annotations
The ISO object identifier (OID) for the coding system, as found at the HL7 OID Registry: https://www.hl7.org/oid/index.cfm
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="OID" type="string_Stype">
  <xs:annotation>
    <xs:documentation>The ISO object identifier (OID) for the coding system, as found at the HL7 OID Registry: https://www.hl7.org/oid/index.cfm</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodeSystemType / CodeSystemURI
Namespace urn:ihe:qrph:sdc:2016
Annotations
Web resource that uniquely identifies the coding system
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element minOccurs="0" name="CodeSystemURI" type="anyURI_Stype">
  <xs:annotation>
    <xs:documentation>Web resource that uniquely identifies the coding system</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodingType / CodeURI
Namespace urn:ihe:qrph:sdc:2016
Annotations
NEW: Web resource that provides information about the code
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element minOccurs="0" name="CodeURI" type="anyURI_Stype">
  <xs:annotation>
    <xs:documentation>NEW: Web resource that provides information about the code</xs:documentation>
  </xs:annotation>
</xs:element>
Element CodingType / Units
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#UnitsType_unitSystem SDCResources_xsd.tmp#UnitsType
Type UnitsType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Default Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
unitSystem xs:string UCUM optional
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Units" type="UnitsType">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
</xs:element>
Element LinkType / LinkText
Namespace urn:ihe:qrph:sdc:2016
Annotations
A description of the URI link, usually for display purposes.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#RichTextType_val SDCResources_xsd.tmp#RichTextType_RichText SDCResources_xsd.tmp#RichTextType
Type RichTextType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Extension, Property, RichText
Instance
<LinkText name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <RichText name="" order="" styleClass="" type="">{1,1}</RichText>
</LinkText>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element minOccurs="0" name="LinkText" type="RichTextType">
  <xs:annotation>
    <xs:documentation>A description of the URI link, usually for display purposes.</xs:documentation>
  </xs:annotation>
</xs:element>
Element LinkType / LinkURI
Namespace urn:ihe:qrph:sdc:2016
Annotations
Link to external information.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="LinkURI" type="anyURI_Stype">
  <xs:annotation>
    <xs:documentation>Link to external information.</xs:documentation>
  </xs:annotation>
</xs:element>
Element BlobType / Description
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#RichTextType_val SDCResources_xsd.tmp#RichTextType_RichText SDCResources_xsd.tmp#RichTextType
Type RichTextType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Property, RichText
Instance
<Description name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <RichText name="" order="" styleClass="" type="">{1,1}</RichText>
</Description>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Description" type="RichTextType"/>
Element BlobType / Hash
Namespace urn:ihe:qrph:sdc:2016
Annotations
Binary hash of the blob data
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#base64Binary_Stype_mimeType SDCDataTypes_xsd.tmp#base64Binary_Stype_val SDCDataTypes_xsd.tmp#base64Binary_Stype SDCResources_xsd.tmp#HashType_hashAlgorithm SDCResources_xsd.tmp#HashType
Type HashType
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
hashAlgorithm xs:string optional
mimeType xs:string optional
TBD: Must be a valid MIME type
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:base64Binary optional
Source
<xs:element name="Hash" minOccurs="0" type="HashType">
  <xs:annotation>
    <xs:documentation>Binary hash of the blob data</xs:documentation>
  </xs:annotation>
</xs:element>
Element BlobType / BlobURI
Namespace urn:ihe:qrph:sdc:2016
Annotations
This URI should contain a URL or web service link
to the Blob. It is used instead of incorporating the Blob
directly into XML templates.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element name="BlobURI" type="anyURI_Stype">
  <xs:annotation>
    <xs:documentation>This URI should contain a URL or web service link to the Blob. It is used instead of incorporating the Blob directly into XML templates.</xs:documentation>
  </xs:annotation>
</xs:element>
Element BlobType / BinaryMediaBase64
Namespace urn:ihe:qrph:sdc:2016
Annotations
Binary represeentation of the Blob data, encoded
using a Base 64 transformation from the original source binary
data. Base 64 encoding uses 64 character alphanumeric text
(characters A–Z, a–z, 0–9, =, /) to represent the binary data,
so that it may be transmitted as "text" inside an XML instance
document without the need for escape
characters.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#base64Binary_Stype_mimeType SDCDataTypes_xsd.tmp#base64Binary_Stype_val SDCDataTypes_xsd.tmp#base64Binary_Stype
Type base64Binary_Stype
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
mimeType xs:string optional
TBD: Must be a valid MIME type
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:base64Binary optional
Source
<xs:element name="BinaryMediaBase64" type="base64Binary_Stype">
  <xs:annotation>
    <xs:documentation>Binary represeentation of the Blob data, encoded using a Base 64 transformation from the original source binary data. Base 64 encoding uses 64 character alphanumeric text (characters A–Z, a–z, 0–9, =, /) to represent the binary data, so that it may be transmitted as "text" inside an XML instance document without the need for escape characters.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ContactType / Person
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PersonType_PersonName SDCResources_xsd.tmp#PersonType_AliasName SDCResources_xsd.tmp#PersonType_Job SDCResources_xsd.tmp#PersonType_StreetAddress SDCResources_xsd.tmp#PersonType_Email SDCResources_xsd.tmp#PersonType_Phone SDCResources_xsd.tmp#PersonType_WebURL SDCResources_xsd.tmp#PersonType_Role SDCResources_xsd.tmp#PersonType_Identifier SDCResources_xsd.tmp#PersonType_Usage SDCResources_xsd.tmp#PersonType
Type PersonType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children AliasName, Comment, Email, Extension, Identifier, Job, PersonName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<Person name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <PersonName name="" order="" styleClass="" type="">{1,1}</PersonName>
  <AliasName name="" order="" styleClass="" type="">{0,unbounded}</AliasName>
  <Job name="" order="" styleClass="" type="">{0,unbounded}</Job>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,1}</Role>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Person>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="Person" type="PersonType"/>
Element PersonType / PersonName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#NameType_NamePrefix SDCResources_xsd.tmp#NameType_FirstName SDCResources_xsd.tmp#NameType_MiddleName SDCResources_xsd.tmp#NameType_LastName SDCResources_xsd.tmp#NameType_NameSuffix SDCResources_xsd.tmp#NameType_DegreeCert SDCResources_xsd.tmp#NameType_Title SDCResources_xsd.tmp#NameType
Type NameType
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children Comment, DegreeCert, Extension, FirstName, LastName, MiddleName, NamePrefix, NameSuffix, Property, Title
Instance
<PersonName name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <NamePrefix name="" order="" styleClass="" type="" val="">{0,1}</NamePrefix>
  <FirstName name="" order="" styleClass="" type="" val="">{1,1}</FirstName>
  <MiddleName name="" order="" styleClass="" type="" val="">{0,1}</MiddleName>
  <LastName name="" order="" styleClass="" type="" val="">{1,1}</LastName>
  <NameSuffix name="" order="" styleClass="" type="" val="">{0,1}</NameSuffix>
  <DegreeCert name="" order="" styleClass="" type="" val="">{0,unbounded}</DegreeCert>
  <Title name="" order="" styleClass="" type="" val="">{0,1}</Title>
</PersonName>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="1" name="PersonName" type="NameType">
</xs:element>
Element NameType / NamePrefix
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="NamePrefix" type="string_Stype" minOccurs="0"/>
Element NameType / FirstName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="FirstName" type="string_Stype" nillable="true"/>
Element NameType / MiddleName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="MiddleName" type="string_Stype" minOccurs="0"/>
Element NameType / LastName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="LastName" type="string_Stype" nillable="true"/>
Element NameType / NameSuffix
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="NameSuffix" type="string_Stype" minOccurs="0"/>
Element NameType / DegreeCert
Namespace urn:ihe:qrph:sdc:2016
Annotations
Acronyms for degrees and certifications, e.g., MD, PhD, FACP (repeat element for each acronym)
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="DegreeCert" type="string_Stype" maxOccurs="unbounded" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Acronyms for degrees and certifications, e.g., MD, PhD, FACP (repeat element for each acronym)</xs:documentation>
  </xs:annotation>
</xs:element>
Element NameType / Title
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="Title" type="string_Stype" minOccurs="0"/>
Element PersonType / AliasName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#NameType_NamePrefix SDCResources_xsd.tmp#NameType_FirstName SDCResources_xsd.tmp#NameType_MiddleName SDCResources_xsd.tmp#NameType_LastName SDCResources_xsd.tmp#NameType_NameSuffix SDCResources_xsd.tmp#NameType_DegreeCert SDCResources_xsd.tmp#NameType_Title SDCResources_xsd.tmp#NameType
Type NameType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, DegreeCert, Extension, FirstName, LastName, MiddleName, NamePrefix, NameSuffix, Property, Title
Instance
<AliasName name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <NamePrefix name="" order="" styleClass="" type="" val="">{0,1}</NamePrefix>
  <FirstName name="" order="" styleClass="" type="" val="">{1,1}</FirstName>
  <MiddleName name="" order="" styleClass="" type="" val="">{0,1}</MiddleName>
  <LastName name="" order="" styleClass="" type="" val="">{1,1}</LastName>
  <NameSuffix name="" order="" styleClass="" type="" val="">{0,1}</NameSuffix>
  <DegreeCert name="" order="" styleClass="" type="" val="">{0,unbounded}</DegreeCert>
  <Title name="" order="" styleClass="" type="" val="">{0,1}</Title>
</AliasName>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="AliasName" type="NameType">
</xs:element>
Element PersonType / Job
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#JobType_JobTitle SDCResources_xsd.tmp#JobType_Organization SDCResources_xsd.tmp#JobType_StartDate SDCResources_xsd.tmp#JobType_StopDate SDCResources_xsd.tmp#JobType_Description SDCResources_xsd.tmp#JobType
Type JobType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Description, Extension, JobTitle, Organization, Property, StartDate, StopDate
Instance
<Job name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <JobTitle name="" order="" styleClass="" type="" val="">{0,unbounded}</JobTitle>
  <Organization name="" order="" styleClass="" type="">{0,1}</Organization>
  <StartDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</StartDate>
  <StopDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</StopDate>
  <Description name="" order="" styleClass="" type="" val="">{0,1}</Description>
</Job>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Job" type="JobType"/>
Element JobType / JobTitle
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="JobTitle" type="string_Stype"/>
Element JobType / Organization
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#OrganizationType_OrgName SDCResources_xsd.tmp#OrganizationType_Department SDCResources_xsd.tmp#OrganizationType_StreetAddress SDCResources_xsd.tmp#OrganizationType_Email SDCResources_xsd.tmp#OrganizationType_Phone SDCResources_xsd.tmp#OrganizationType_WebURL SDCResources_xsd.tmp#OrganizationType_Role SDCResources_xsd.tmp#OrganizationType_ContactPerson SDCResources_xsd.tmp#OrganizationType_Identifier SDCResources_xsd.tmp#OrganizationType_Usage SDCResources_xsd.tmp#OrganizationType
Type OrganizationType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, ContactPerson, Department, Email, Extension, Identifier, OrgName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<Organization name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <OrgName name="" order="" styleClass="" type="" val="">{1,1}</OrgName>
  <Department name="" order="" styleClass="" type="" val="">{0,1}</Department>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,unbounded}</Role>
  <ContactPerson name="" order="" styleClass="" type="">{0,unbounded}</ContactPerson>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Organization>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
Element OrganizationType / OrgName
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="OrgName" type="string_Stype" nillable="true"/>
Element OrganizationType / Department
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Department" type="string_Stype"/>
Element OrganizationType / StreetAddress
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#AddressType_AddressType SDCResources_xsd.tmp#AddressType_InternalAddress SDCResources_xsd.tmp#AddressType_AddressLine SDCResources_xsd.tmp#AddressType_City SDCResources_xsd.tmp#AddressType_Jurisdiction SDCResources_xsd.tmp#AddressType_State SDCResources_xsd.tmp#AddressType_PostalCode SDCResources_xsd.tmp#AddressType_Country SDCResources_xsd.tmp#AddressType_Usage SDCResources_xsd.tmp#AddressType
Type AddressType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children AddressLine, AddressType, City, Comment, Country, Extension, InternalAddress, Jurisdiction, PostalCode, Property, State, Usage
Instance
<StreetAddress name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <AddressType name="" order="" styleClass="" type="" val="">{0,1}</AddressType>
  <InternalAddress name="" order="" styleClass="" type="" val="">{0,10}</InternalAddress>
  <AddressLine name="" order="" styleClass="" type="" val="">{0,10}</AddressLine>
  <City name="" order="" styleClass="" type="" val="">{0,1}</City>
  <Jurisdiction name="" order="" styleClass="" type="" val="">{0,1}</Jurisdiction>
  <State name="" order="" styleClass="" type="" val="">{0,1}</State>
  <PostalCode name="" order="" styleClass="" type="" val="">{0,1}</PostalCode>
  <Country name="" order="" styleClass="" type="" val="">{0,1}</Country>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</StreetAddress>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="StreetAddress" type="AddressType"/>
Element AddressType / AddressType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Type of address, e.g., home, office, etc
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="AddressType" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Type of address, e.g., home, office, etc</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / InternalAddress
Namespace urn:ihe:qrph:sdc:2016
Annotations
Address instructions for directing mail within an organizations buildings or corporate
infrastructure.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 10
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="10" minOccurs="0" name="InternalAddress" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Address instructions for directing mail within an organizations buildings or corporate infrastructure.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / AddressLine
Namespace urn:ihe:qrph:sdc:2016
Annotations
Address instructions for directing mail to a street address.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 10
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="10" minOccurs="0" name="AddressLine" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Address instructions for directing mail to a street address.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / City
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="City" type="string_Stype"/>
Element AddressType / Jurisdiction
Namespace urn:ihe:qrph:sdc:2016
Annotations
Other optional locale identifier.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Jurisdiction" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Other optional locale identifier.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / State
Namespace urn:ihe:qrph:sdc:2016
Annotations
State, Province, etc.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="State" type="string_Stype">
  <xs:annotation>
    <xs:documentation>State, Province, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / PostalCode
Namespace urn:ihe:qrph:sdc:2016
Annotations
Local postal code, e.g., zip code.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="PostalCode" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Local postal code, e.g., zip code.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / Country
Namespace urn:ihe:qrph:sdc:2016
Annotations
**Need list of official country codes or text?
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Country" type="string_Stype">
  <xs:annotation>
    <xs:documentation>**Need list of official country codes or text?</xs:documentation>
  </xs:annotation>
</xs:element>
Element AddressType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
When this address should be used
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
  <xs:annotation>
    <xs:documentation>When this address should be used</xs:documentation>
  </xs:annotation>
</xs:element>
Element OrganizationType / Email
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#EmailType_EmailAddress SDCResources_xsd.tmp#EmailType_EmailClass SDCResources_xsd.tmp#EmailType_Usage SDCResources_xsd.tmp#EmailType
Type EmailType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, EmailAddress, EmailClass, Extension, Property, Usage
Instance
<Email name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <EmailAddress name="" order="" styleClass="" type="" val="">{1,1}</EmailAddress>
  <EmailClass name="" order="" styleClass="" type="" val="">{0,1}</EmailClass>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Email>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Email" type="EmailType"/>
Element EmailType / EmailAddress
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#EmailAddressType_val SDCResources_xsd.tmp#EmailAddressType
Type EmailAddressType
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Model
Children Comment, Extension, Property
Instance
<EmailAddress name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
</EmailAddress>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val EmailAddress_Stype required
Source
<xs:element maxOccurs="1" minOccurs="1" name="EmailAddress" type="EmailAddressType">
</xs:element>
Element EmailType / EmailClass
Namespace urn:ihe:qrph:sdc:2016
Annotations
Type of email, e.g., home, office, etc
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="EmailClass" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Type of email, e.g., home, office, etc</xs:documentation>
  </xs:annotation>
</xs:element>
Element EmailType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
When this email should be used
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
  <xs:annotation>
    <xs:documentation>When this email should be used</xs:documentation>
  </xs:annotation>
</xs:element>
Element OrganizationType / Phone
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PhoneType_PhoneType SDCResources_xsd.tmp#PhoneType_CountryCode SDCResources_xsd.tmp#PhoneType_AreaCode SDCResources_xsd.tmp#PhoneType_PhoneNumber SDCResources_xsd.tmp#PhoneType_PhoneExtension SDCResources_xsd.tmp#PhoneType_Usage SDCResources_xsd.tmp#PhoneType
Type PhoneType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children AreaCode, Comment, CountryCode, Extension, PhoneExtension, PhoneNumber, PhoneType, Property, Usage
Instance
<Phone name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <PhoneType name="" order="" styleClass="" type="" val="">{0,1}</PhoneType>
  <CountryCode name="" order="" styleClass="" type="" val="">{0,1}</CountryCode>
  <AreaCode name="" order="" styleClass="" type="" val="">{0,1}</AreaCode>
  <PhoneNumber name="" order="" styleClass="" type="" val="">{1,1}</PhoneNumber>
  <PhoneExtension name="" order="" styleClass="" type="" val="">{0,1}</PhoneExtension>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Phone>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Phone" type="PhoneType"/>
Element PhoneType / PhoneType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Usage type of phone number, e.g., home, office, etc
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="PhoneType" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Usage type of phone number, e.g., home, office, etc</xs:documentation>
  </xs:annotation>
</xs:element>
Element PhoneType / CountryCode
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#CountryCodeType_val SDCResources_xsd.tmp#CountryCodeType
Type CountryCodeType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val CountryCode_Stype required
Source
<xs:element maxOccurs="1" minOccurs="0" name="CountryCode" type="CountryCodeType">
</xs:element>
Element PhoneType / AreaCode
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#AreaCodeType_val SDCResources_xsd.tmp#AreaCodeType
Type AreaCodeType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val AreaCode_Stype optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="AreaCode" type="AreaCodeType">
</xs:element>
Element PhoneType / PhoneNumber
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PhoneNumberType_val SDCResources_xsd.tmp#PhoneNumberType
Type PhoneNumberType
Type hierarchy
Properties
content complex
Model
Children Comment, Extension, Property
Instance
<PhoneNumber name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
</PhoneNumber>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val PhoneNumber_Stype required
Source
<xs:element name="PhoneNumber" type="PhoneNumberType">
</xs:element>
Element PhoneType / PhoneExtension
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="PhoneExtension" type="string_Stype"/>
Element PhoneType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
When this phone number should be used
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
  <xs:annotation>
    <xs:documentation>When this phone number should be used</xs:documentation>
  </xs:annotation>
</xs:element>
Element OrganizationType / WebURL
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="WebURL" type="anyURI_Stype">
</xs:element>
Element OrganizationType / Role
Namespace urn:ihe:qrph:sdc:2016
Annotations
Role of the organization, e.g., creator, copyright
holder, accreditor, certifier, curator, etc.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Role" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Role of the organization, e.g., creator, copyright holder, accreditor, certifier, curator, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OrganizationType / ContactPerson
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PersonType_PersonName SDCResources_xsd.tmp#PersonType_AliasName SDCResources_xsd.tmp#PersonType_Job SDCResources_xsd.tmp#PersonType_StreetAddress SDCResources_xsd.tmp#PersonType_Email SDCResources_xsd.tmp#PersonType_Phone SDCResources_xsd.tmp#PersonType_WebURL SDCResources_xsd.tmp#PersonType_Role SDCResources_xsd.tmp#PersonType_Identifier SDCResources_xsd.tmp#PersonType_Usage SDCResources_xsd.tmp#PersonType
Type PersonType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children AliasName, Comment, Email, Extension, Identifier, Job, PersonName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<ContactPerson name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <PersonName name="" order="" styleClass="" type="">{1,1}</PersonName>
  <AliasName name="" order="" styleClass="" type="">{0,unbounded}</AliasName>
  <Job name="" order="" styleClass="" type="">{0,unbounded}</Job>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,1}</Role>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</ContactPerson>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="ContactPerson" type="PersonType"/>
Element PersonType / StreetAddress
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#AddressType_AddressType SDCResources_xsd.tmp#AddressType_InternalAddress SDCResources_xsd.tmp#AddressType_AddressLine SDCResources_xsd.tmp#AddressType_City SDCResources_xsd.tmp#AddressType_Jurisdiction SDCResources_xsd.tmp#AddressType_State SDCResources_xsd.tmp#AddressType_PostalCode SDCResources_xsd.tmp#AddressType_Country SDCResources_xsd.tmp#AddressType_Usage SDCResources_xsd.tmp#AddressType
Type AddressType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children AddressLine, AddressType, City, Comment, Country, Extension, InternalAddress, Jurisdiction, PostalCode, Property, State, Usage
Instance
<StreetAddress name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <AddressType name="" order="" styleClass="" type="" val="">{0,1}</AddressType>
  <InternalAddress name="" order="" styleClass="" type="" val="">{0,10}</InternalAddress>
  <AddressLine name="" order="" styleClass="" type="" val="">{0,10}</AddressLine>
  <City name="" order="" styleClass="" type="" val="">{0,1}</City>
  <Jurisdiction name="" order="" styleClass="" type="" val="">{0,1}</Jurisdiction>
  <State name="" order="" styleClass="" type="" val="">{0,1}</State>
  <PostalCode name="" order="" styleClass="" type="" val="">{0,1}</PostalCode>
  <Country name="" order="" styleClass="" type="" val="">{0,1}</Country>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</StreetAddress>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="StreetAddress" type="AddressType"/>
Element PersonType / Email
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#EmailType_EmailAddress SDCResources_xsd.tmp#EmailType_EmailClass SDCResources_xsd.tmp#EmailType_Usage SDCResources_xsd.tmp#EmailType
Type EmailType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, EmailAddress, EmailClass, Extension, Property, Usage
Instance
<Email name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <EmailAddress name="" order="" styleClass="" type="" val="">{1,1}</EmailAddress>
  <EmailClass name="" order="" styleClass="" type="" val="">{0,1}</EmailClass>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Email>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Email" type="EmailType"/>
Element PersonType / Phone
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PhoneType_PhoneType SDCResources_xsd.tmp#PhoneType_CountryCode SDCResources_xsd.tmp#PhoneType_AreaCode SDCResources_xsd.tmp#PhoneType_PhoneNumber SDCResources_xsd.tmp#PhoneType_PhoneExtension SDCResources_xsd.tmp#PhoneType_Usage SDCResources_xsd.tmp#PhoneType
Type PhoneType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children AreaCode, Comment, CountryCode, Extension, PhoneExtension, PhoneNumber, PhoneType, Property, Usage
Instance
<Phone name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <PhoneType name="" order="" styleClass="" type="" val="">{0,1}</PhoneType>
  <CountryCode name="" order="" styleClass="" type="" val="">{0,1}</CountryCode>
  <AreaCode name="" order="" styleClass="" type="" val="">{0,1}</AreaCode>
  <PhoneNumber name="" order="" styleClass="" type="" val="">{1,1}</PhoneNumber>
  <PhoneExtension name="" order="" styleClass="" type="" val="">{0,1}</PhoneExtension>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Phone>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Phone" type="PhoneType"/>
Element PersonType / WebURL
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="WebURL" type="anyURI_Stype">
</xs:element>
Element PersonType / Role
Namespace urn:ihe:qrph:sdc:2016
Annotations
Role of the person, e.g., creator, copyright holder, accreditor, certifier, curator, etc.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Role" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Role of the person, e.g., creator, copyright holder, accreditor, certifier, curator, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element PersonType / Identifier
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#IdentifierType_system SDCResources_xsd.tmp#IdentifierType_val SDCResources_xsd.tmp#IdentifierType
Type IdentifierType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Property
Instance
<Identifier name="" order="" styleClass="" system="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
</Identifier>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
system xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element name="Identifier" type="IdentifierType" maxOccurs="unbounded" minOccurs="0"/>
Element PersonType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
When this person should be contacted.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
  <xs:annotation>
    <xs:documentation>When this person should be contacted.</xs:documentation>
  </xs:annotation>
</xs:element>
Element OrganizationType / Identifier
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#IdentifierType_system SDCResources_xsd.tmp#IdentifierType_val SDCResources_xsd.tmp#IdentifierType
Type IdentifierType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Property
Instance
<Identifier name="" order="" styleClass="" system="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
</Identifier>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
system xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element name="Identifier" type="IdentifierType" maxOccurs="unbounded" minOccurs="0"/>
Element OrganizationType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
When this organization should be
contacted.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
  <xs:annotation>
    <xs:documentation>When this organization should be contacted.</xs:documentation>
  </xs:annotation>
</xs:element>
Element JobType / StartDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#date_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#date_Stype
Type date_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:date optional
Source
<xs:element minOccurs="0" name="StartDate" type="date_Stype"/>
Element JobType / StopDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#date_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#date_Stype
Type date_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:date optional
Source
<xs:element minOccurs="0" name="StopDate" type="date_Stype"/>
Element JobType / Description
Namespace urn:ihe:qrph:sdc:2016
Annotations
Job Description
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Description" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Job Description</xs:documentation>
  </xs:annotation>
</xs:element>
Element ContactType / Organization
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#OrganizationType_OrgName SDCResources_xsd.tmp#OrganizationType_Department SDCResources_xsd.tmp#OrganizationType_StreetAddress SDCResources_xsd.tmp#OrganizationType_Email SDCResources_xsd.tmp#OrganizationType_Phone SDCResources_xsd.tmp#OrganizationType_WebURL SDCResources_xsd.tmp#OrganizationType_Role SDCResources_xsd.tmp#OrganizationType_ContactPerson SDCResources_xsd.tmp#OrganizationType_Identifier SDCResources_xsd.tmp#OrganizationType_Usage SDCResources_xsd.tmp#OrganizationType
Type OrganizationType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, ContactPerson, Department, Email, Extension, Identifier, OrgName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<Organization name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <OrgName name="" order="" styleClass="" type="" val="">{1,1}</OrgName>
  <Department name="" order="" styleClass="" type="" val="">{0,1}</Department>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,unbounded}</Role>
  <ContactPerson name="" order="" styleClass="" type="">{0,unbounded}</ContactPerson>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Organization>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
Element DataTypes_DEType / anyType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyType_DEtype_minLength SDCDataTypes_xsd.tmp#anyType_DEtype_maxLength SDCDataTypes_xsd.tmp#anyType_DEtype_schema SDCDataTypes_xsd.tmp#anyType_DEtype_namespace SDCDataTypes_xsd.tmp#anyType_DEtype
Type anyType_DEtype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace
Attributes
QName Type Use Annotation
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
namespace xs:string optional
Namespace used in an XML Schema file, if any, used to constrain and validate the the content of this field.  This is similar to the use of namespaces with the xs:any element in XML Schemas.

See: http://www.w3.org/TR/xmlschema-0/#any
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
schema xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace
Source
<xs:element name="anyType" nillable="true" type="anyType_DEtype">
</xs:element>
Element DataTypes_DEType / anyURI
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype SDCDataTypes_xsd.tmp#anyURI_DEtype_length SDCDataTypes_xsd.tmp#anyURI_DEtype_minLength SDCDataTypes_xsd.tmp#anyURI_DEtype_maxLength SDCDataTypes_xsd.tmp#anyURI_DEtype_pattern SDCDataTypes_xsd.tmp#anyURI_DEtype
Type anyURI_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
length xs:long optional
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
pattern xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element name="anyURI" nillable="true" type="anyURI_DEtype">
</xs:element>
Element DataTypes_DEType / base64Binary
Namespace urn:ihe:qrph:sdc:2016
Annotations
**SDC may need a valid list of MIME types.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#base64Binary_Stype_mimeType SDCDataTypes_xsd.tmp#base64Binary_Stype_val SDCDataTypes_xsd.tmp#base64Binary_Stype SDCDataTypes_xsd.tmp#base64Binary_DEtype_minLength SDCDataTypes_xsd.tmp#base64Binary_DEtype_maxLength SDCDataTypes_xsd.tmp#base64Binary_DEtype
Type base64Binary_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
maxLength xs:long optional
mimeType xs:string optional
TBD: Must be a valid MIME type
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:base64Binary optional
Source
<xs:element name="base64Binary" nillable="true" type="base64Binary_DEtype">
  <xs:annotation>
    <xs:documentation>**SDC may need a valid list of MIME types.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_DEType / boolean
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#boolean_Stype_val SDCDataTypes_xsd.tmp#boolean_Stype SDCDataTypes_xsd.tmp#boolean_DEtype
Type boolean_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:boolean optional
Source
<xs:element name="boolean" nillable="true" type="boolean_DEtype">
</xs:element>
Element DataTypes_DEType / duration
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

Duration Data Type 
The duration data type is used to specify a time interval.
The time interval is specified in the following form
"PnYnMnDTnHnMnS" where: 
 P indicates the period (required) 
 nY indicates the number of years nM indicates the number of months 
 nD indicates the number of days T indicates the start of a time section
 (required if you are going to specify hours, minutes, or seconds) 
 nH indicates the number of hours nM indicates the number of minutes 
 nS indicates the number of seconds 

An element in your document might look like this: P5Y 
 The example above indicates a period of five years. 
 
Or it might look like this: P5Y2M10D. 
 The example above indicates a period of five years, two months, and 10 days. 
 
Or it might look like this: P5Y2M10DT15H. 
 The example above indicates a period of five years, two months, 10 days, and 15 hours. 
 
Or it might look like this: PT15H.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#duration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#duration_Stype SDCDataTypes_xsd.tmp#duration_DEtype_minInclusive SDCDataTypes_xsd.tmp#duration_DEtype_maxInclusive SDCDataTypes_xsd.tmp#duration_DEtype_minExclusive SDCDataTypes_xsd.tmp#duration_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#duration_DEtype
Type duration_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:duration optional
maxInclusive xs:duration optional
minExclusive xs:duration optional
minInclusive xs:duration optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="duration" nillable="true" type="duration_DEtype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_DEType / byte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#byte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#byte_Stype SDCDataTypes_xsd.tmp#byte_DEtype_minInclusive SDCDataTypes_xsd.tmp#byte_DEtype_maxInclusive SDCDataTypes_xsd.tmp#byte_DEtype_minExclusive SDCDataTypes_xsd.tmp#byte_DEtype_maxExclusive SDCDataTypes_xsd.tmp#byte_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#byte_DEtype
Type byte_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:byte optional
maxInclusive xs:byte optional
minExclusive xs:byte optional
minInclusive xs:byte optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:byte optional
Source
<xs:element name="byte" nillable="true" type="byte_DEtype">
</xs:element>
Element DataTypes_DEType / date
Namespace urn:ihe:qrph:sdc:2016
Annotations
**Does SDC need a list of valid patterns for all date/time types?
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#date_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#date_Stype SDCDataTypes_xsd.tmp#date_DEtype_minInclusive SDCDataTypes_xsd.tmp#date_DEtype_maxInclusive SDCDataTypes_xsd.tmp#date_DEtype_minExclusive SDCDataTypes_xsd.tmp#date_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#date_DEtype
Type date_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:date optional
maxInclusive xs:date optional
minExclusive xs:date optional
minInclusive xs:date optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:date optional
Source
<xs:element name="date" nillable="true" type="date_DEtype">
  <xs:annotation>
    <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_DEType / dateTimeStamp
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxInclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minInclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype
Type dateTimeStamp_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxExclusive xs:dateTime optional
maxInclusive xs:dateTime optional
minExclusive xs:dateTime optional
minInclusive xs:dateTime optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_DEtype">
</xs:element>
Element DataTypes_DEType / decimal
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#decimal_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#decimal_Stype SDCDataTypes_xsd.tmp#decimal_DEtype_minInclusive SDCDataTypes_xsd.tmp#decimal_DEtype_maxInclusive SDCDataTypes_xsd.tmp#decimal_DEtype_minExclusive SDCDataTypes_xsd.tmp#decimal_DEtype_maxExclusive SDCDataTypes_xsd.tmp#decimal_DEtype_fractionDigits SDCDataTypes_xsd.tmp#decimal_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#decimal_DEtype
Type decimal_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:decimal optional
maxInclusive xs:decimal optional
minExclusive xs:decimal optional
minInclusive xs:decimal optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:decimal optional
Source
<xs:element name="decimal" nillable="true" type="decimal_DEtype">
</xs:element>
Element DataTypes_DEType / dateTime
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

DateTime Data Type 
The dateTime data type is used to specify a date
 and a time. The dateTime is specified in the following form
 "YYYY-MM-DDThh:mm:ss" where: 
 YYYY indicates the year 
 MM indicates the month 
 DD indicates the day 
 T indicates the start of the required time section 
 hh indicates the hour 
 mm indicates the minute 
 ss indicates the second 
 
Time Zones 
 To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time -
 like this: 09:30:10Z 
 or you can specify an offset from the UTC time by adding a positive or negative time behind the
 time - like this: 09:30:10-06:00 or 09:30:10+06:00.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxInclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minInclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype
Type dateTimeStamp_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxExclusive xs:dateTime optional
maxInclusive xs:dateTime optional
minExclusive xs:dateTime optional
minInclusive xs:dateTime optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTime" nillable="true" type="dateTimeStamp_DEtype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_DEType / double
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#double_Stype_val SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#double_Stype SDCDataTypes_xsd.tmp#double_DEtype_minInclusive SDCDataTypes_xsd.tmp#double_DEtype_maxInclusive SDCDataTypes_xsd.tmp#double_DEtype_minExclusive SDCDataTypes_xsd.tmp#double_DEtype_maxExclusive SDCDataTypes_xsd.tmp#double_DEtype_fractionDigits SDCDataTypes_xsd.tmp#double_DEtype_totalDigits SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#double_DEtype
Type double_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:double optional
maxInclusive xs:double optional
minExclusive xs:double optional
minInclusive xs:double optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:double optional
Source
<xs:element name="double" nillable="true" type="double_DEtype"/>
Element DataTypes_DEType / float
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#float_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#float_Stype SDCDataTypes_xsd.tmp#float_DEtype_minInclusive SDCDataTypes_xsd.tmp#float_DEtype_maxInclusive SDCDataTypes_xsd.tmp#float_DEtype_minExclusive SDCDataTypes_xsd.tmp#float_DEtype_maxExclusive SDCDataTypes_xsd.tmp#float_DEtype_fractionDigits SDCDataTypes_xsd.tmp#float_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#float_DEtype
Type float_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:float optional
maxInclusive xs:float optional
minExclusive xs:float optional
minInclusive xs:float optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:float optional
Source
<xs:element name="float" nillable="true" type="float_DEtype"/>
Element DataTypes_DEType / gDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gDay_Stype SDCDataTypes_xsd.tmp#gDay_DEtype_minInclusive SDCDataTypes_xsd.tmp#gDay_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gDay_DEtype_minExclusive SDCDataTypes_xsd.tmp#gDay_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gDay_DEtype
Type gDay_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gDay optional
maxInclusive xs:gDay optional
minExclusive xs:gDay optional
minInclusive xs:gDay optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gDay optional
Source
<xs:element name="gDay" nillable="true" type="gDay_DEtype"/>
Element DataTypes_DEType / gMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype SDCDataTypes_xsd.tmp#gMonth_DEtype_minInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_minExclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gMonth_DEtype
Type gMonth_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gMonth optional
maxInclusive xs:gMonth optional
minExclusive xs:gMonth optional
minInclusive xs:gMonth optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gMonth" nillable="true" type="gMonth_DEtype"/>
Element DataTypes_DEType / gMonthDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonthDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonthDay_Stype SDCDataTypes_xsd.tmp#gMonthDay_DEtype_minInclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_minExclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gMonthDay_DEtype
Type gMonthDay_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gMonthDay optional
maxInclusive xs:gMonthDay optional
minExclusive xs:gMonthDay optional
minInclusive xs:gMonthDay optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonthDay optional
Source
<xs:element name="gMonthDay" nillable="true" type="gMonthDay_DEtype"/>
Element DataTypes_DEType / gYear
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gYear_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gYear_Stype SDCDataTypes_xsd.tmp#gYear_DEtype_minInclusive SDCDataTypes_xsd.tmp#gYear_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gYear_DEtype_minExclusive SDCDataTypes_xsd.tmp#gYear_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gYear_DEtype
Type gYear_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gYear optional
maxInclusive xs:gYear optional
minExclusive xs:gYear optional
minInclusive xs:gYear optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gYear optional
Source
<xs:element name="gYear" nillable="true" type="gYear_DEtype"/>
Element DataTypes_DEType / gYearMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype SDCDataTypes_xsd.tmp#gMonth_DEtype_minInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_minExclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gMonth_DEtype
Type gMonth_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gMonth optional
maxInclusive xs:gMonth optional
minExclusive xs:gMonth optional
minInclusive xs:gMonth optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gYearMonth" nillable="true" type="gMonth_DEtype"/>
Element DataTypes_DEType / hexBinary
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#hexBinary_Stype_mimeType SDCDataTypes_xsd.tmp#hexBinary_Stype_val SDCDataTypes_xsd.tmp#hexBinary_Stype SDCDataTypes_xsd.tmp#hexBinary_DEtype_minLength SDCDataTypes_xsd.tmp#hexBinary_DEtype_maxLength SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#hexBinary_DEtype
Type hexBinary_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxLength xs:long optional
mimeType xs:string optional
TBD: Must be a valid MIME type - needs
enumeration
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:hexBinary optional
Source
<xs:element name="hexBinary" nillable="true" type="hexBinary_DEtype"/>
Element DataTypes_DEType / HTML
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#HTML_Stype SDCDataTypes_xsd.tmp#HTML_DEtype_minLength SDCDataTypes_xsd.tmp#HTML_DEtype_maxLength SDCDataTypes_xsd.tmp#HTML_DEtype
Type HTML_DEtype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Attributes
QName Type Use Annotation
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Wildcard: ANY attribute from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Source
<xs:element name="HTML" nillable="true" type="HTML_DEtype">
</xs:element>
Element DataTypes_DEType / int
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#int_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#int_Stype SDCDataTypes_xsd.tmp#int_DEtype_minInclusive SDCDataTypes_xsd.tmp#int_DEtype_maxInclusive SDCDataTypes_xsd.tmp#int_DEtype_minExclusive SDCDataTypes_xsd.tmp#int_DEtype_maxExclusive SDCDataTypes_xsd.tmp#int_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#int_DEtype
Type int_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:int optional
maxInclusive xs:int optional
minExclusive xs:int optional
minInclusive xs:int optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:int optional
Source
<xs:element name="int" nillable="true" type="int_DEtype">
</xs:element>
Element DataTypes_DEType / integer
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#integer_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#integer_Stype SDCDataTypes_xsd.tmp#integer_DEtype_maxExclusive SDCDataTypes_xsd.tmp#integer_DEtype_minExclusive SDCDataTypes_xsd.tmp#integer_DEtype_maxInclusive SDCDataTypes_xsd.tmp#integer_DEtype_minInclusive SDCDataTypes_xsd.tmp#integer_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#integer_DEtype
Type integer_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:integer optional
maxInclusive xs:integer optional
minExclusive xs:integer optional
minInclusive xs:integer optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:integer optional
Source
<xs:element name="integer" nillable="true" type="integer_DEtype">
</xs:element>
Element DataTypes_DEType / long
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#long_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#long_Stype SDCDataTypes_xsd.tmp#long_DEtype_minInclusive SDCDataTypes_xsd.tmp#long_DEtype_maxInclusive SDCDataTypes_xsd.tmp#long_DEtype_minExclusive SDCDataTypes_xsd.tmp#long_DEtype_maxExclusive SDCDataTypes_xsd.tmp#long_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#long_DEtype
Type long_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:long optional
maxInclusive xs:long optional
minExclusive xs:long optional
minInclusive xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:long optional
Source
<xs:element name="long" nillable="true" type="long_DEtype">
</xs:element>
Element DataTypes_DEType / negativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#negativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#negativeInteger_Stype SDCDataTypes_xsd.tmp#negativeInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#negativeInteger_DEtype
Type negativeInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:negativeInteger optional
maxInclusive xs:negativeInteger optional
minExclusive xs:negativeInteger optional
minInclusive xs:negativeInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:negativeInteger optional
Source
<xs:element name="negativeInteger" nillable="true" type="negativeInteger_DEtype"/>
Element DataTypes_DEType / nonNegativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype
Type nonNegativeInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:nonNegativeInteger optional
maxInclusive xs:nonNegativeInteger optional
minExclusive xs:nonNegativeInteger optional
minInclusive xs:nonNegativeInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonNegativeInteger optional
Source
<xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_DEtype"/>
Element DataTypes_DEType / nonPositiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype
Type nonPositiveInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:nonPositiveInteger optional
maxInclusive xs:nonPositiveInteger optional
minExclusive xs:nonPositiveInteger optional
minInclusive xs:nonPositiveInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonPositiveInteger optional
Source
<xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_DEtype"/>
Element DataTypes_DEType / positiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#positiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#positiveInteger_Stype SDCDataTypes_xsd.tmp#positiveInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#positiveInteger_DEtype
Type positiveInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:positiveInteger optional
maxInclusive xs:positiveInteger optional
minExclusive xs:positiveInteger optional
minInclusive xs:positiveInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:positiveInteger optional
Source
<xs:element name="positiveInteger" nillable="true" type="positiveInteger_DEtype"/>
Element DataTypes_DEType / short
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#short_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#short_Stype SDCDataTypes_xsd.tmp#short_DEtype_minInclusive SDCDataTypes_xsd.tmp#short_DEtype_maxInclusive SDCDataTypes_xsd.tmp#short_DEtype_minExclusive SDCDataTypes_xsd.tmp#short_DEtype_maxExclusive SDCDataTypes_xsd.tmp#short_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#short_DEtype
Type short_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:short optional
maxInclusive xs:short optional
minExclusive xs:short optional
minInclusive xs:short optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:short optional
Source
<xs:element name="short" nillable="true" type="short_DEtype"/>
Element DataTypes_DEType / string
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCDataTypes_xsd.tmp#string_DEtype_minLength SDCDataTypes_xsd.tmp#string_DEtype_maxLength SDCDataTypes_xsd.tmp#string_DEtype_pattern SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#string_DEtype
Type string_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
pattern xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="string" nillable="true" type="string_DEtype"/>
Element DataTypes_DEType / time
Namespace urn:ihe:qrph:sdc:2016
Annotations
**possibly "HH:MM:SS:ms am/pm 12/24"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#time_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#time_Stype SDCDataTypes_xsd.tmp#time_DEtype_minInclusive SDCDataTypes_xsd.tmp#time_DEtype_maxInclusive SDCDataTypes_xsd.tmp#time_DEtype_minExclusive SDCDataTypes_xsd.tmp#time_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#time_DEtype
Type time_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:time optional
maxInclusive xs:time optional
minExclusive xs:time optional
minInclusive xs:time optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:time optional
Source
<xs:element name="time" nillable="true" type="time_DEtype">
  <xs:annotation>
    <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypes_DEType / unsignedByte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedByte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedByte_Stype SDCDataTypes_xsd.tmp#unsignedByte_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedByte_DEtype
Type unsignedByte_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedByte optional
maxInclusive xs:unsignedByte optional
minExclusive xs:unsignedByte optional
minInclusive xs:unsignedByte optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedByte optional
Source
<xs:element name="unsignedByte" nillable="true" type="unsignedByte_DEtype"/>
Element DataTypes_DEType / unsignedInt
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedInt_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedInt_Stype SDCDataTypes_xsd.tmp#unsignedInt_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedInt_DEtype
Type unsignedInt_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedInt optional
maxInclusive xs:unsignedInt optional
minExclusive xs:unsignedInt optional
minInclusive xs:unsignedInt optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedInt optional
Source
<xs:element name="unsignedInt" nillable="true" type="unsignedInt_DEtype"/>
Element DataTypes_DEType / unsignedLong
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedLong_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedLong_Stype SDCDataTypes_xsd.tmp#unsignedLong_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedLong_DEtype
Type unsignedLong_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedLong optional
maxInclusive xs:unsignedLong optional
minExclusive xs:unsignedLong optional
minInclusive xs:unsignedLong optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedLong optional
Source
<xs:element name="unsignedLong" nillable="true" type="unsignedLong_DEtype"/>
Element DataTypes_DEType / unsignedShort
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedShort_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedShort_Stype SDCDataTypes_xsd.tmp#unsignedShort_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedShort_DEtype
Type unsignedShort_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedShort optional
maxInclusive xs:unsignedShort optional
minExclusive xs:unsignedShort optional
minInclusive xs:unsignedShort optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedShort optional
Source
<xs:element name="unsignedShort" nillable="true" type="unsignedShort_DEtype"/>
Element DataTypes_DEType / XML
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#XML_Stype_schema SDCDataTypes_xsd.tmp#XML_Stype SDCDataTypes_xsd.tmp#XML_DEtype_minLength SDCDataTypes_xsd.tmp#XML_DEtype_maxLength SDCDataTypes_xsd.tmp#XML_DEtype
Type XML_DEtype
Type hierarchy
Properties
content complex
nillable true
Model
ANY element from ANY namespace OTHER than 'urn:ihe:qrph:sdc:2016'
Attributes
QName Type Use Annotation
maxLength xs:long optional
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
schema xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="XML" nillable="true" type="XML_DEtype"/>
Element DataTypes_DEType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minExclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype
Type yearMonthDuration_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:duration optional
maxInclusive xs:duration optional
minExclusive xs:duration optional
minInclusive xs:duration optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
</xs:element>
Element FileType / FileID
Namespace urn:ihe:qrph:sdc:2016
Annotations
Internal/local File ID, not necessarily in the format
of the FileURI used for all SDC FormDesign items.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="FileID" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Internal/local File ID, not necessarily in the format of the FileURI used for all SDC FormDesign items.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileURI
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element minOccurs="1" name="FileURI" type="anyURI_Stype"/>
Element FileType / DisplayName
Namespace urn:ihe:qrph:sdc:2016
Annotations
Text to be displayed that encapulates the file
contents. This may be the same as the internal Title of the
file.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="DisplayName" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Text to be displayed that encapulates the file contents. This may be the same as the internal Title of the file.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / Title
Namespace urn:ihe:qrph:sdc:2016
Annotations
Official title of the file.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="Title" type="string_Stype" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Official title of the file.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / Version
Namespace urn:ihe:qrph:sdc:2016
Annotations
File version
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#versionAttributes SDCResources_xsd.tmp#VersionType_VersioningReference SDCResources_xsd.tmp#VersionType_VersionComments SDCResources_xsd.tmp#VersionType_Changes SDCResources_xsd.tmp#VersionType
Type VersionType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Changes, Comment, Extension, Property, VersionComments, VersioningReference
Instance
<Version fullVersion="" name="" order="" styleClass="" type="" versionLevel.1="" versionLevel.2="" versionLevel.3="" versionLevel.4="" versionLevel.5="" versionRegExPattern="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <VersioningReference name="" order="" styleClass="" type="">{0,1}</VersioningReference>
  <VersionComments name="" order="" styleClass="" type="" val="">{0,1}</VersionComments>
  <Changes name="" order="" styleClass="" type="">{0,1}</Changes>
</Version>
Attributes
QName Type Use Annotation
fullVersion xs:string required
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
versionLevel.1 xs:string optional
Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.
versionLevel.2 xs:string optional
versionLevel.3 xs:string optional
versionLevel.4 xs:string optional
versionLevel.5 xs:string optional
versionRegExPattern xs:string required
Regular Expression that determines the format of the Full Version
Source
<xs:element minOccurs="0" name="Version" type="VersionType">
  <xs:annotation>
    <xs:documentation>File version</xs:documentation>
  </xs:annotation>
</xs:element>
Element VersionType / VersioningReference
Namespace urn:ihe:qrph:sdc:2016
Annotations
Information about the document that describes the versioning methodology nomenclature.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileType_FileID SDCResources_xsd.tmp#FileType_FileURI SDCResources_xsd.tmp#FileType_DisplayName SDCResources_xsd.tmp#FileType_Title SDCResources_xsd.tmp#FileType_Version SDCResources_xsd.tmp#FileType_FileName SDCResources_xsd.tmp#FileType_FileExtension SDCResources_xsd.tmp#FileType_FileClass SDCResources_xsd.tmp#FileType_FileSizeKB SDCResources_xsd.tmp#FileType_Description SDCResources_xsd.tmp#FileType_Copyright SDCResources_xsd.tmp#FileType_TermsofUse SDCResources_xsd.tmp#FileType_Usage SDCResources_xsd.tmp#FileType_Dates SDCResources_xsd.tmp#FileType_Contacts SDCResources_xsd.tmp#FileType_Approval SDCResources_xsd.tmp#FileType_FileHash SDCResources_xsd.tmp#FileType_Language SDCResources_xsd.tmp#FileType_AssociatedFiles SDCResources_xsd.tmp#FileType_Provenance SDCResources_xsd.tmp#FileType_DefaultSubmissionRule SDCResources_xsd.tmp#FileType_DefaultComplianceRule SDCResources_xsd.tmp#FileType
Type FileType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Approval, AssociatedFiles, Comment, Contacts, Copyright, Dates, DefaultComplianceRule, DefaultSubmissionRule, Description, DisplayName, Extension, FileClass, FileExtension, FileHash, FileID, FileName, FileSizeKB, FileURI, Language, Property, Provenance, TermsofUse, Title, Usage, Version
Instance
<VersioningReference name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <FileID name="" order="" styleClass="" type="" val="">{0,1}</FileID>
  <FileURI name="" order="" styleClass="" type="" val="">{1,1}</FileURI>
  <DisplayName name="" order="" styleClass="" type="" val="">{1,1}</DisplayName>
  <Title name="" order="" styleClass="" type="" val="">{0,1}</Title>
  <Version fullVersion="" name="" order="" styleClass="" type="" versionLevel.1="" versionLevel.2="" versionLevel.3="" versionLevel.4="" versionLevel.5="" versionRegExPattern="">{0,1}</Version>
  <FileName name="" order="" styleClass="" type="" val="">{0,1}</FileName>
  <FileExtension name="" order="" styleClass="" type="" val="">{0,1}</FileExtension>
  <FileClass name="" order="" styleClass="" type="" val="">{0,1}</FileClass>
  <FileSizeKB name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</FileSizeKB>
  <Description name="" order="" styleClass="" type="" val="">{0,unbounded}</Description>
  <Copyright name="" order="" styleClass="" type="" val="">{0,1}</Copyright>
  <TermsofUse name="" order="" styleClass="" type="" val="">{0,1}</TermsofUse>
  <Usage name="" order="" styleClass="" type="">{0,1}</Usage>
  <Dates name="" order="" styleClass="" type="">{0,1}</Dates>
  <Contacts name="" order="" styleClass="" type="">{0,1}</Contacts>
  <Approval name="" order="" styleClass="" type="">{0,unbounded}</Approval>
  <FileHash hashType="" name="" order="" styleClass="" type="" val="">{0,1}</FileHash>
  <Language name="" order="" styleClass="" type="">{0,unbounded}</Language>
  <AssociatedFiles name="" order="" styleClass="" type="">{0,1}</AssociatedFiles>
  <Provenance name="" order="" styleClass="" type="">{0,1}</Provenance>
  <DefaultSubmissionRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultSubmissionRule>
  <DefaultComplianceRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultComplianceRule>
</VersioningReference>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="VersioningReference" type="FileType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Information about the document that describes the versioning methodology nomenclature.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileName
Namespace urn:ihe:qrph:sdc:2016
Annotations
The name of the file as saved on disk or other persistant storage.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="FileName" type="string_Stype">
  <xs:annotation>
    <xs:documentation>The name of the file as saved on disk or other persistant storage.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileExtension
Namespace urn:ihe:qrph:sdc:2016
Annotations
The file type extension that describes the file's
internal format. This is usually the 3-4 character text that appears
after the last period in the file name, e.g., txt, docx,
etc.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="FileExtension" type="string_Stype">
  <xs:annotation>
    <xs:documentation>The file type extension that describes the file's internal format. This is usually the 3-4 character text that appears after the last period in the file name, e.g., txt, docx, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileClass
Namespace urn:ihe:qrph:sdc:2016
Annotations
A short description of the class of file, such as "FormDesign XML"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="FileClass" type="string_Stype">
  <xs:annotation>
    <xs:documentation>A short description of the class of file, such as "FormDesign XML"</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileSizeKB
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#positiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#positiveInteger_Stype
Type positiveInteger_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:positiveInteger optional
Source
<xs:element minOccurs="0" name="FileSizeKB" type="positiveInteger_Stype">
</xs:element>
Element FileType / Description
Namespace urn:ihe:qrph:sdc:2016
Annotations
Any additional information about the template or file. The type of information should be specified in the @type
attribute.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
nillable false
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Any additional information about the template or file. The type of information should be specified in the @type attribute.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / Copyright
Namespace urn:ihe:qrph:sdc:2016
Diagram
Type string_Stype
Type hierarchy
Properties
Attributes
Source
Element FileType / TermsofUse
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="TermsofUse" type="string_Stype"/>
Element FileType / Usage
Namespace urn:ihe:qrph:sdc:2016
Annotations
Guidance for when this file should be used, and when it should not be used.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileUsageType_Included SDCResources_xsd.tmp#FileUsageType_Excluded SDCResources_xsd.tmp#FileUsageType_Description SDCResources_xsd.tmp#FileUsageType
Type FileUsageType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Description, Excluded, Extension, Included, Property
Instance
<Usage name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Included name="" order="" styleClass="" type="">{0,unbounded}</Included>
  <Excluded name="" order="" styleClass="" type="">{0,unbounded}</Excluded>
  <Description name="" order="" styleClass="" type="" val="">{0,unbounded}</Description>
</Usage>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="Usage" type="FileUsageType">
  <xs:annotation>
    <xs:documentation>Guidance for when this file should be used, and when it should not be used.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileUsageType / Included
Namespace urn:ihe:qrph:sdc:2016
Annotations
Reasons to use the file
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#CodingType_Code SDCResources_xsd.tmp#CodingType_TypedValue SDCResources_xsd.tmp#CodingType_CodeText SDCResources_xsd.tmp#CodingType_CodeMatch SDCResources_xsd.tmp#CodingType_CodeSystem SDCResources_xsd.tmp#CodingType_CodeURI SDCResources_xsd.tmp#CodingType_Units SDCResources_xsd.tmp#CodingType
Type CodingType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Code, CodeMatch, CodeSystem, CodeText, CodeURI, Comment, Extension, Property, TypedValue, Units
Instance
<Included name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Code name="" order="" styleClass="" type="" val="">{1,1}</Code>
  <TypedValue name="" order="" styleClass="" type="">{0,1}</TypedValue>
  <CodeText name="" order="" styleClass="" type="" val="">{0,1}</CodeText>
  <CodeMatch codeMatchEnum="Exact Code Match" name="" order="" styleClass="" type="">{0,1}</CodeMatch>
  <CodeSystem name="" order="" styleClass="" type="">{0,1}</CodeSystem>
  <CodeURI name="" order="" styleClass="" type="" val="">{0,1}</CodeURI>
  <Units name="" order="" styleClass="" type="" unitSystem="UCUM" val="">{0,1}</Units>
</Included>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Included" type="CodingType">
  <xs:annotation>
    <xs:documentation>Reasons to use the file</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileUsageType / Excluded
Namespace urn:ihe:qrph:sdc:2016
Annotations
Reasons to not use the file
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#CodingType_Code SDCResources_xsd.tmp#CodingType_TypedValue SDCResources_xsd.tmp#CodingType_CodeText SDCResources_xsd.tmp#CodingType_CodeMatch SDCResources_xsd.tmp#CodingType_CodeSystem SDCResources_xsd.tmp#CodingType_CodeURI SDCResources_xsd.tmp#CodingType_Units SDCResources_xsd.tmp#CodingType
Type CodingType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Code, CodeMatch, CodeSystem, CodeText, CodeURI, Comment, Extension, Property, TypedValue, Units
Instance
<Excluded name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Code name="" order="" styleClass="" type="" val="">{1,1}</Code>
  <TypedValue name="" order="" styleClass="" type="">{0,1}</TypedValue>
  <CodeText name="" order="" styleClass="" type="" val="">{0,1}</CodeText>
  <CodeMatch codeMatchEnum="Exact Code Match" name="" order="" styleClass="" type="">{0,1}</CodeMatch>
  <CodeSystem name="" order="" styleClass="" type="">{0,1}</CodeSystem>
  <CodeURI name="" order="" styleClass="" type="" val="">{0,1}</CodeURI>
  <Units name="" order="" styleClass="" type="" unitSystem="UCUM" val="">{0,1}</Units>
</Excluded>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Excluded" type="CodingType">
  <xs:annotation>
    <xs:documentation>Reasons to not use the file</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileUsageType / Description
Namespace urn:ihe:qrph:sdc:2016
Annotations
Non-coded text describing usage criteria.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
nillable false
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Non-coded text describing usage criteria.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / Dates
Namespace urn:ihe:qrph:sdc:2016
Annotations
Various dates associated with the file release, versioning and usage.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileDatesType_FileDate SDCResources_xsd.tmp#FileDatesType_PreviousRevisionDate SDCResources_xsd.tmp#FileDatesType_ReleaseDate SDCResources_xsd.tmp#FileDatesType_EffectiveDate SDCResources_xsd.tmp#FileDatesType_FirstReleaseDate SDCResources_xsd.tmp#FileDatesType_UsageStartDate SDCResources_xsd.tmp#FileDatesType_RetirementDate SDCResources_xsd.tmp#FileDatesType_OtherDate SDCResources_xsd.tmp#FileDatesType
Type FileDatesType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, EffectiveDate, Extension, FileDate, FirstReleaseDate, OtherDate, PreviousRevisionDate, Property, ReleaseDate, RetirementDate, UsageStartDate
Instance
<Dates name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <FileDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</FileDate>
  <PreviousRevisionDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,unbounded}</PreviousRevisionDate>
  <ReleaseDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</ReleaseDate>
  <EffectiveDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</EffectiveDate>
  <FirstReleaseDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</FirstReleaseDate>
  <UsageStartDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</UsageStartDate>
  <RetirementDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</RetirementDate>
  <OtherDate name="" order="" quantEnum="" styleClass="" type="" val="">{0,unbounded}</OtherDate>
</Dates>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="Dates" type="FileDatesType">
  <xs:annotation>
    <xs:documentation>Various dates associated with the file release, versioning and usage.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileDatesType / FileDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="FileDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / PreviousRevisionDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="PreviousRevisionDate" maxOccurs="unbounded" type="dateTime_Stype">
</xs:element>
Element FileDatesType / ReleaseDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="ReleaseDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / EffectiveDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="EffectiveDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / FirstReleaseDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="FirstReleaseDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / UsageStartDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="UsageStartDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / RetirementDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="RetirementDate" type="dateTime_Stype">
</xs:element>
Element FileDatesType / OtherDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element minOccurs="0" name="OtherDate" maxOccurs="unbounded" type="dateTime_Stype">
</xs:element>
Element FileType / Contacts
Namespace urn:ihe:qrph:sdc:2016
Annotations
People and Organizations associated with the file.
Specify the type of Contact in the @type attribute. Examples of
@type include Curator, Author, and Authority.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactsType_Contact SDCResources_xsd.tmp#ContactsType
Type ContactsType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Contact, Extension, Property
Instance
<Contacts name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Contact name="" order="" styleClass="" type="">{1,unbounded}</Contact>
</Contacts>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="Contacts" type="ContactsType">
  <xs:annotation>
    <xs:documentation>People and Organizations associated with the file. Specify the type of Contact in the @type attribute. Examples of @type include Curator, Author, and Authority.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ContactsType / Contact
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactType_Person SDCResources_xsd.tmp#ContactType_Organization SDCResources_xsd.tmp#ContactType
Type ContactType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children Comment, Extension, Organization, Person, Property
Instance
<Contact name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Person name="" order="" styleClass="" type="">{0,1}</Person>
  <Organization name="" order="" styleClass="" type="">{0,1}</Organization>
</Contact>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" name="Contact" type="ContactType"/>
Element FileType / Approval
Namespace urn:ihe:qrph:sdc:2016
Annotations
Documentation of review and acceptance of the file for production usage.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ApprovalType_ApprovalContact SDCResources_xsd.tmp#ApprovalType_Description SDCResources_xsd.tmp#ApprovalType
Type ApprovalType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children ApprovalContact, Comment, Description, Extension, Property
Instance
<Approval name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <ApprovalContact name="" order="" styleClass="" type="">{0,unbounded}</ApprovalContact>
  <Description name="" order="" styleClass="" type="" val="">{0,unbounded}</Description>
</Approval>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="Approval" maxOccurs="unbounded" type="ApprovalType">
  <xs:annotation>
    <xs:documentation>Documentation of review and acceptance of the file for production usage.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ApprovalType / ApprovalContact
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactType_Person SDCResources_xsd.tmp#ContactType_Organization SDCResources_xsd.tmp#ContactType
Type ContactType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Organization, Person, Property
Instance
<ApprovalContact name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Person name="" order="" styleClass="" type="">{0,1}</Person>
  <Organization name="" order="" styleClass="" type="">{0,1}</Organization>
</ApprovalContact>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" name="ApprovalContact" type="ContactType" minOccurs="0"/>
Element ApprovalType / Description
Namespace urn:ihe:qrph:sdc:2016
Annotations
Non-structured text describing file approval.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
nillable false
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
  <xs:annotation>
    <xs:documentation>Non-structured text describing file approval.</xs:documentation>
  </xs:annotation>
</xs:element>
Element FileType / FileHash
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#FileHashType_hashType SDCResources_xsd.tmp#FileHashType
Type FileHashType
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
hashType xs:string optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="FileHash" type="FileHashType">
</xs:element>
Element FileType / Language
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#LanguageType_Language SDCResources_xsd.tmp#LanguageType_LanguageCode.ISO.639.3 SDCResources_xsd.tmp#LanguageType
Type LanguageType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Extension, Language, LanguageCode.ISO.639.3, Property
Instance
<Language name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Language name="" order="" styleClass="" type="" val="">{0,1}</Language>
  <LanguageCode.ISO.639.3 name="" order="" styleClass="" type="" val="">{1,1}</LanguageCode.ISO.639.3>
</Language>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="Language" type="LanguageType"/>
Element LanguageType / Language
Namespace urn:ihe:qrph:sdc:2016
Annotations
The language used for text in SDC templates.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="0" name="Language" type="string_Stype">
  <xs:annotation>
    <xs:documentation>The language used for text in SDC templates.</xs:documentation>
  </xs:annotation>
</xs:element>
Element LanguageType / LanguageCode.ISO.639.3
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#LanguageCode.ISO.639.3_Type_val SDCResources_xsd.tmp#LanguageCode.ISO.639.3_Type
Type LanguageCode.ISO.639.3_Type
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val LanguageCode.ISO.639.3_StypeEnum required
Source
<xs:element name="LanguageCode.ISO.639.3" type="LanguageCode.ISO.639.3_Type">
</xs:element>
Element FileType / AssociatedFiles
Namespace urn:ihe:qrph:sdc:2016
Annotations
Link to any associated files, such as schemas, reference documents, manuals, etc.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#AssociatedFilesType_File SDCResources_xsd.tmp#AssociatedFilesType
Type AssociatedFilesType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Extension, File, Property
Instance
<AssociatedFiles name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <File name="" order="" styleClass="" type="">{1,unbounded}</File>
</AssociatedFiles>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="AssociatedFiles" type="AssociatedFilesType">
  <xs:annotation>
    <xs:documentation>Link to any associated files, such as schemas, reference documents, manuals, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Element AssociatedFilesType / File
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileType_FileID SDCResources_xsd.tmp#FileType_FileURI SDCResources_xsd.tmp#FileType_DisplayName SDCResources_xsd.tmp#FileType_Title SDCResources_xsd.tmp#FileType_Version SDCResources_xsd.tmp#FileType_FileName SDCResources_xsd.tmp#FileType_FileExtension SDCResources_xsd.tmp#FileType_FileClass SDCResources_xsd.tmp#FileType_FileSizeKB SDCResources_xsd.tmp#FileType_Description SDCResources_xsd.tmp#FileType_Copyright SDCResources_xsd.tmp#FileType_TermsofUse SDCResources_xsd.tmp#FileType_Usage SDCResources_xsd.tmp#FileType_Dates SDCResources_xsd.tmp#FileType_Contacts SDCResources_xsd.tmp#FileType_Approval SDCResources_xsd.tmp#FileType_FileHash SDCResources_xsd.tmp#FileType_Language SDCResources_xsd.tmp#FileType_AssociatedFiles SDCResources_xsd.tmp#FileType_Provenance SDCResources_xsd.tmp#FileType_DefaultSubmissionRule SDCResources_xsd.tmp#FileType_DefaultComplianceRule SDCResources_xsd.tmp#FileType
Type FileType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children Approval, AssociatedFiles, Comment, Contacts, Copyright, Dates, DefaultComplianceRule, DefaultSubmissionRule, Description, DisplayName, Extension, FileClass, FileExtension, FileHash, FileID, FileName, FileSizeKB, FileURI, Language, Property, Provenance, TermsofUse, Title, Usage, Version
Instance
<File name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <FileID name="" order="" styleClass="" type="" val="">{0,1}</FileID>
  <FileURI name="" order="" styleClass="" type="" val="">{1,1}</FileURI>
  <DisplayName name="" order="" styleClass="" type="" val="">{1,1}</DisplayName>
  <Title name="" order="" styleClass="" type="" val="">{0,1}</Title>
  <Version fullVersion="" name="" order="" styleClass="" type="" versionLevel.1="" versionLevel.2="" versionLevel.3="" versionLevel.4="" versionLevel.5="" versionRegExPattern="">{0,1}</Version>
  <FileName name="" order="" styleClass="" type="" val="">{0,1}</FileName>
  <FileExtension name="" order="" styleClass="" type="" val="">{0,1}</FileExtension>
  <FileClass name="" order="" styleClass="" type="" val="">{0,1}</FileClass>
  <FileSizeKB name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</FileSizeKB>
  <Description name="" order="" styleClass="" type="" val="">{0,unbounded}</Description>
  <Copyright name="" order="" styleClass="" type="" val="">{0,1}</Copyright>
  <TermsofUse name="" order="" styleClass="" type="" val="">{0,1}</TermsofUse>
  <Usage name="" order="" styleClass="" type="">{0,1}</Usage>
  <Dates name="" order="" styleClass="" type="">{0,1}</Dates>
  <Contacts name="" order="" styleClass="" type="">{0,1}</Contacts>
  <Approval name="" order="" styleClass="" type="">{0,unbounded}</Approval>
  <FileHash hashType="" name="" order="" styleClass="" type="" val="">{0,1}</FileHash>
  <Language name="" order="" styleClass="" type="">{0,unbounded}</Language>
  <AssociatedFiles name="" order="" styleClass="" type="">{0,1}</AssociatedFiles>
  <Provenance name="" order="" styleClass="" type="">{0,1}</Provenance>
  <DefaultSubmissionRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultSubmissionRule>
  <DefaultComplianceRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultComplianceRule>
</File>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="File" type="FileType" maxOccurs="unbounded"/>
Element FileType / Provenance
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ProvenanceType_ReplacedFile SDCResources_xsd.tmp#ProvenanceType
Type ProvenanceType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Extension, Property, ReplacedFile
Instance
<Provenance name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <ReplacedFile name="" order="" styleClass="" type="">{1,unbounded}</ReplacedFile>
</Provenance>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="Provenance" type="ProvenanceType">
</xs:element>
Element ProvenanceType / ReplacedFile
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileType_FileID SDCResources_xsd.tmp#FileType_FileURI SDCResources_xsd.tmp#FileType_DisplayName SDCResources_xsd.tmp#FileType_Title SDCResources_xsd.tmp#FileType_Version SDCResources_xsd.tmp#FileType_FileName SDCResources_xsd.tmp#FileType_FileExtension SDCResources_xsd.tmp#FileType_FileClass SDCResources_xsd.tmp#FileType_FileSizeKB SDCResources_xsd.tmp#FileType_Description SDCResources_xsd.tmp#FileType_Copyright SDCResources_xsd.tmp#FileType_TermsofUse SDCResources_xsd.tmp#FileType_Usage SDCResources_xsd.tmp#FileType_Dates SDCResources_xsd.tmp#FileType_Contacts SDCResources_xsd.tmp#FileType_Approval SDCResources_xsd.tmp#FileType_FileHash SDCResources_xsd.tmp#FileType_Language SDCResources_xsd.tmp#FileType_AssociatedFiles SDCResources_xsd.tmp#FileType_Provenance SDCResources_xsd.tmp#FileType_DefaultSubmissionRule SDCResources_xsd.tmp#FileType_DefaultComplianceRule SDCResources_xsd.tmp#FileType
Type FileType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children Approval, AssociatedFiles, Comment, Contacts, Copyright, Dates, DefaultComplianceRule, DefaultSubmissionRule, Description, DisplayName, Extension, FileClass, FileExtension, FileHash, FileID, FileName, FileSizeKB, FileURI, Language, Property, Provenance, TermsofUse, Title, Usage, Version
Instance
<ReplacedFile name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <FileID name="" order="" styleClass="" type="" val="">{0,1}</FileID>
  <FileURI name="" order="" styleClass="" type="" val="">{1,1}</FileURI>
  <DisplayName name="" order="" styleClass="" type="" val="">{1,1}</DisplayName>
  <Title name="" order="" styleClass="" type="" val="">{0,1}</Title>
  <Version fullVersion="" name="" order="" styleClass="" type="" versionLevel.1="" versionLevel.2="" versionLevel.3="" versionLevel.4="" versionLevel.5="" versionRegExPattern="">{0,1}</Version>
  <FileName name="" order="" styleClass="" type="" val="">{0,1}</FileName>
  <FileExtension name="" order="" styleClass="" type="" val="">{0,1}</FileExtension>
  <FileClass name="" order="" styleClass="" type="" val="">{0,1}</FileClass>
  <FileSizeKB name="" order="" quantEnum="" styleClass="" type="" val="">{0,1}</FileSizeKB>
  <Description name="" order="" styleClass="" type="" val="">{0,unbounded}</Description>
  <Copyright name="" order="" styleClass="" type="" val="">{0,1}</Copyright>
  <TermsofUse name="" order="" styleClass="" type="" val="">{0,1}</TermsofUse>
  <Usage name="" order="" styleClass="" type="">{0,1}</Usage>
  <Dates name="" order="" styleClass="" type="">{0,1}</Dates>
  <Contacts name="" order="" styleClass="" type="">{0,1}</Contacts>
  <Approval name="" order="" styleClass="" type="">{0,unbounded}</Approval>
  <FileHash hashType="" name="" order="" styleClass="" type="" val="">{0,1}</FileHash>
  <Language name="" order="" styleClass="" type="">{0,unbounded}</Language>
  <AssociatedFiles name="" order="" styleClass="" type="">{0,1}</AssociatedFiles>
  <Provenance name="" order="" styleClass="" type="">{0,1}</Provenance>
  <DefaultSubmissionRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultSubmissionRule>
  <DefaultComplianceRule formID="" name="" order="" ruleID="" styleClass="" type="">{0,unbounded}</DefaultComplianceRule>
</ReplacedFile>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="ReplacedFile" type="FileType" maxOccurs="unbounded"/>
Element FileType / DefaultSubmissionRule
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#SubmissionRuleType_formID SDCResources_xsd.tmp#SubmissionRuleType_ruleID SDCResources_xsd.tmp#SubmissionRuleType_Destination SDCResources_xsd.tmp#SubmissionRuleType_RuleDescription SDCResources_xsd.tmp#SubmissionRuleType
Type SubmissionRuleType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, Destination, Extension, Property, RuleDescription
Instance
<DefaultSubmissionRule formID="" name="" order="" ruleID="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Destination name="" order="" styleClass="" type="">{1,unbounded}</Destination>
  <RuleDescription name="" order="" styleClass="" type="" val="">{0,1}</RuleDescription>
</DefaultSubmissionRule>
Attributes
QName Type Use Annotation
formID URI_Atype optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
ruleID URI_Atype required
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="DefaultSubmissionRule" type="SubmissionRuleType"/>
Element SubmissionRuleType / Destination
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DestinationType_Endpoint SDCResources_xsd.tmp#DestinationType_EndpointDescription SDCResources_xsd.tmp#DestinationType_SubmissionTechnology SDCResources_xsd.tmp#DestinationType_Organization SDCResources_xsd.tmp#DestinationType
Type DestinationType
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children Comment, Endpoint, EndpointDescription, Extension, Organization, Property, SubmissionTechnology
Instance
<Destination name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Endpoint name="" order="" styleClass="" type="" val="">{1,1}</Endpoint>
  <EndpointDescription name="" order="" styleClass="" type="" val="">{1,1}</EndpointDescription>
  <SubmissionTechnology name="" order="" styleClass="" type="" val="">{0,unbounded}</SubmissionTechnology>
  <Organization name="" order="" styleClass="" type="">{0,1}</Organization>
</Destination>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="1" name="Destination" type="DestinationType">
</xs:element>
Element DestinationType / Endpoint
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="Endpoint" type="anyURI_Stype"/>
Element DestinationType / EndpointDescription
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="EndpointDescription" type="string_Stype"/>
Element DestinationType / SubmissionTechnology
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="SubmissionTechnology" type="string_Stype"/>
Element DestinationType / Organization
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#OrganizationType_OrgName SDCResources_xsd.tmp#OrganizationType_Department SDCResources_xsd.tmp#OrganizationType_StreetAddress SDCResources_xsd.tmp#OrganizationType_Email SDCResources_xsd.tmp#OrganizationType_Phone SDCResources_xsd.tmp#OrganizationType_WebURL SDCResources_xsd.tmp#OrganizationType_Role SDCResources_xsd.tmp#OrganizationType_ContactPerson SDCResources_xsd.tmp#OrganizationType_Identifier SDCResources_xsd.tmp#OrganizationType_Usage SDCResources_xsd.tmp#OrganizationType
Type OrganizationType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children Comment, ContactPerson, Department, Email, Extension, Identifier, OrgName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<Organization name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <OrgName name="" order="" styleClass="" type="" val="">{1,1}</OrgName>
  <Department name="" order="" styleClass="" type="" val="">{0,1}</Department>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,unbounded}</Role>
  <ContactPerson name="" order="" styleClass="" type="">{0,unbounded}</ContactPerson>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</Organization>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
Element SubmissionRuleType / RuleDescription
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element minOccurs="0" name="RuleDescription" type="string_Stype"/>
Element FileType / DefaultComplianceRule
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ComplianceRuleType_ruleID SDCResources_xsd.tmp#ComplianceRuleType_formID SDCResources_xsd.tmp#ComplianceRuleType_Description SDCResources_xsd.tmp#ComplianceRuleType_ComplianceOrganization SDCResources_xsd.tmp#ComplianceRuleType
Type ComplianceRuleType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, ComplianceOrganization, Description, Extension, Property
Instance
<DefaultComplianceRule formID="" name="" order="" ruleID="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Description name="" order="" styleClass="" type="" val="">{1,1}</Description>
  <ComplianceOrganization name="" order="" styleClass="" type="">{0,unbounded}</ComplianceOrganization>
</DefaultComplianceRule>
Attributes
QName Type Use Annotation
formID URI_Atype optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
ruleID URI_Atype required
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="DefaultComplianceRule" type="ComplianceRuleType"/>
Element ComplianceRuleType / Description
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="1" minOccurs="1" name="Description" type="string_Stype"/>
Element ComplianceRuleType / ComplianceOrganization
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#OrganizationType_OrgName SDCResources_xsd.tmp#OrganizationType_Department SDCResources_xsd.tmp#OrganizationType_StreetAddress SDCResources_xsd.tmp#OrganizationType_Email SDCResources_xsd.tmp#OrganizationType_Phone SDCResources_xsd.tmp#OrganizationType_WebURL SDCResources_xsd.tmp#OrganizationType_Role SDCResources_xsd.tmp#OrganizationType_ContactPerson SDCResources_xsd.tmp#OrganizationType_Identifier SDCResources_xsd.tmp#OrganizationType_Usage SDCResources_xsd.tmp#OrganizationType
Type OrganizationType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children Comment, ContactPerson, Department, Email, Extension, Identifier, OrgName, Phone, Property, Role, StreetAddress, Usage, WebURL
Instance
<ComplianceOrganization name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <OrgName name="" order="" styleClass="" type="" val="">{1,1}</OrgName>
  <Department name="" order="" styleClass="" type="" val="">{0,1}</Department>
  <StreetAddress name="" order="" styleClass="" type="">{0,unbounded}</StreetAddress>
  <Email name="" order="" styleClass="" type="">{0,unbounded}</Email>
  <Phone name="" order="" styleClass="" type="">{0,unbounded}</Phone>
  <WebURL name="" order="" styleClass="" type="" val="">{0,unbounded}</WebURL>
  <Role name="" order="" styleClass="" type="" val="">{0,unbounded}</Role>
  <ContactPerson name="" order="" styleClass="" type="">{0,unbounded}</ContactPerson>
  <Identifier name="" order="" styleClass="" system="" type="" val="">{0,unbounded}</Identifier>
  <Usage name="" order="" styleClass="" type="" val="">{0,1}</Usage>
</ComplianceOrganization>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="ComplianceOrganization" type="OrganizationType"/>
Element VersionType / VersionComments
Namespace urn:ihe:qrph:sdc:2016
Annotations
Comments about the changes in this version
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#RichTextType_val SDCResources_xsd.tmp#RichTextType_RichText SDCResources_xsd.tmp#RichTextType
Type RichTextType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Extension, Property, RichText
Instance
<VersionComments name="" order="" styleClass="" type="" val="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <RichText name="" order="" styleClass="" type="">{1,1}</RichText>
</VersionComments>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:element name="VersionComments" type="RichTextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Comments about the changes in this version</xs:documentation>
  </xs:annotation>
</xs:element>
Element VersionType / Changes
Namespace urn:ihe:qrph:sdc:2016
Annotations
Itemized list of changes in the new version
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#VersionType_VersionType_Changes_Change
Type extension of ExtensionBaseType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Change, Comment, Extension, Property
Instance
<Changes name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Change name="" order="" styleClass="" type="">{1,unbounded}</Change>
</Changes>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="Changes" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Itemized list of changes in the new version</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="ExtensionBaseType">
        <xs:sequence>
          <xs:element name="Change" type="ChangeLogType" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Element VersionType / Changes / Change
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ChangeLogType_ChangedField SDCResources_xsd.tmp#ChangeLogType_ChangedTo SDCResources_xsd.tmp#ChangeLogType_ChangedFrom SDCResources_xsd.tmp#ChangeLogType_ChangeType SDCResources_xsd.tmp#ChangeLogType_Replaces SDCResources_xsd.tmp#ChangeLogType_ChangeDate SDCResources_xsd.tmp#ChangeLogType_ChangeDescription SDCResources_xsd.tmp#ChangeLogType_Editors SDCResources_xsd.tmp#ChangeLogType_ChangeTracking SDCResources_xsd.tmp#ChangeLogType
Type ChangeLogType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children ChangeDate, ChangeDescription, ChangeTracking, ChangeType, ChangedField, ChangedFrom, ChangedTo, Comment, Editors, Extension, Property, Replaces
Instance
<Change name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <ChangedField name="" order="" styleClass="" type="">{1,1}</ChangedField>
  <ChangedTo name="" order="" styleClass="" type="">{1,1}</ChangedTo>
  <ChangedFrom name="" order="" styleClass="" type="">{1,1}</ChangedFrom>
  <ChangeType name="" order="" styleClass="" type="" val="">{1,unbounded}</ChangeType>
  <Replaces name="" order="" styleClass="" type="">{0,1}</Replaces>
  <ChangeDate name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</ChangeDate>
  <ChangeDescription name="" order="" styleClass="" type="" val="">{0,1}</ChangeDescription>
  <Editors name="" order="" styleClass="" type="">{0,1}</Editors>
  <ChangeTracking name="" order="" styleClass="" type="">{0,1}</ChangeTracking>
</Change>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="Change" type="ChangeLogType" maxOccurs="unbounded"/>
Element ChangeLogType / ChangedField
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ItemTarget_TargetItemID SDCResources_xsd.tmp#ItemTarget_TargetItemName SDCResources_xsd.tmp#ItemTarget_TargetItemXPath SDCResources_xsd.tmp#ItemTarget SDCResources_xsd.tmp#ChangedFieldType
Type ChangedFieldType
Type hierarchy
Properties
content complex
Model
Children Comment, Extension, Property, TargetItemID, TargetItemName, TargetItemXPath
Instance
<ChangedField name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <TargetItemID name="" order="" styleClass="" targetItemText="" targetProperty="" type="" val="">{1,1}</TargetItemID>
  <TargetItemName name="" order="" styleClass="" targetItemText="" targetProperty="" type="" val="">{1,1}</TargetItemName>
  <TargetItemXPath name="" order="" styleClass="" targetItemText="" type="" val="">{1,1}</TargetItemXPath>
</ChangedField>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="ChangedField" type="ChangedFieldType">
</xs:element>
Element ItemTarget / TargetItemID
Namespace urn:ihe:qrph:sdc:2016
Annotations
Unique ID of the target item.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype SDCResources_xsd.tmp#TargetItemIDType_targetItemText SDCResources_xsd.tmp#TargetItemIDType_targetProperty SDCResources_xsd.tmp#TargetItemIDType
Type TargetItemIDType
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
targetProperty xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element name="TargetItemID" type="TargetItemIDType">
  <xs:annotation>
    <xs:documentation>Unique ID of the target item.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ItemTarget / TargetItemName
Namespace urn:ihe:qrph:sdc:2016
Annotations
@name attribute of target item. (xs:NCName is the base type of xs:ID)
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#TargetItemNameType_val SDCResources_xsd.tmp#TargetItemNameType_targetItemText SDCResources_xsd.tmp#TargetItemNameType_targetProperty SDCResources_xsd.tmp#TargetItemNameType
Type TargetItemNameType
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
targetProperty xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:NCName optional
Source
<xs:element name="TargetItemName" type="TargetItemNameType">
  <xs:annotation>
    <xs:documentation>@name attribute of target item. (xs:NCName is the base type of xs:ID)</xs:documentation>
  </xs:annotation>
</xs:element>
Element ItemTarget / TargetItemXPath
Namespace urn:ihe:qrph:sdc:2016
Annotations
XPath to target item
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#TargetItemXPathType_targetItemText SDCResources_xsd.tmp#TargetItemXPathType
Type TargetItemXPathType
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="TargetItemXPath" type="TargetItemXPathType">
  <xs:annotation>
    <xs:documentation>XPath to target item</xs:documentation>
  </xs:annotation>
</xs:element>
Element ChangeLogType / ChangedTo
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType
Type DataTypes_SType
Type hierarchy
Properties
content complex
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Instance
<ChangedTo name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <anyType maxLength="" minLength="" name="" namespace="" order="" schema="" styleClass="" type="">{1,1}</anyType>
  <anyURI name="" order="" styleClass="" type="" val="">{1,1}</anyURI>
  <base64Binary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</base64Binary>
  <boolean name="" order="" styleClass="" type="" val="">{1,1}</boolean>
  <duration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</duration>
  <byte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</byte>
  <date name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</date>
  <dateTimeStamp name="" order="" styleClass="" type="" val="">{1,1}</dateTimeStamp>
  <decimal name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</decimal>
  <dateTime name="" order="" styleClass="" type="" val="">{1,1}</dateTime>
  <double mask="" name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</double>
  <float name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</float>
  <gDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gDay>
  <gMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonth>
  <gMonthDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonthDay>
  <gYear name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYear>
  <gYearMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYearMonth>
  <hexBinary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</hexBinary>
  <HTML name="" order="" styleClass="" type="">{1,1}</HTML>
  <int name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</int>
  <integer name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</integer>
  <long name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</long>
  <negativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</negativeInteger>
  <nonNegativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonNegativeInteger>
  <nonPositiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonPositiveInteger>
  <positiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</positiveInteger>
  <short name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</short>
  <string name="" order="" styleClass="" type="" val="">{1,1}</string>
  <time name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</time>
  <unsignedByte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedByte>
  <unsignedInt name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedInt>
  <unsignedLong name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedLong>
  <unsignedShort name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedShort>
  <XML name="" order="" schema="" styleClass="" type="">{1,1}</XML>
  <yearMonthDuration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</yearMonthDuration>
</ChangedTo>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="ChangedTo" type="DataTypes_SType"/>
Element ChangeLogType / ChangedFrom
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType
Type DataTypes_SType
Type hierarchy
Properties
content complex
minOccurs 1
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Instance
<ChangedFrom name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <anyType maxLength="" minLength="" name="" namespace="" order="" schema="" styleClass="" type="">{1,1}</anyType>
  <anyURI name="" order="" styleClass="" type="" val="">{1,1}</anyURI>
  <base64Binary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</base64Binary>
  <boolean name="" order="" styleClass="" type="" val="">{1,1}</boolean>
  <duration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</duration>
  <byte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</byte>
  <date name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</date>
  <dateTimeStamp name="" order="" styleClass="" type="" val="">{1,1}</dateTimeStamp>
  <decimal name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</decimal>
  <dateTime name="" order="" styleClass="" type="" val="">{1,1}</dateTime>
  <double mask="" name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</double>
  <float name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</float>
  <gDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gDay>
  <gMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonth>
  <gMonthDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonthDay>
  <gYear name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYear>
  <gYearMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYearMonth>
  <hexBinary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</hexBinary>
  <HTML name="" order="" styleClass="" type="">{1,1}</HTML>
  <int name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</int>
  <integer name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</integer>
  <long name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</long>
  <negativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</negativeInteger>
  <nonNegativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonNegativeInteger>
  <nonPositiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonPositiveInteger>
  <positiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</positiveInteger>
  <short name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</short>
  <string name="" order="" styleClass="" type="" val="">{1,1}</string>
  <time name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</time>
  <unsignedByte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedByte>
  <unsignedInt name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedInt>
  <unsignedLong name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedLong>
  <unsignedShort name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedShort>
  <XML name="" order="" schema="" styleClass="" type="">{1,1}</XML>
  <yearMonthDuration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</yearMonthDuration>
</ChangedFrom>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="ChangedFrom" type="DataTypes_SType" minOccurs="1"/>
Element ChangeLogType / ChangeType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" name="ChangeType" type="string_Stype"/>
Element ChangeLogType / Replaces
Namespace urn:ihe:qrph:sdc:2016
Annotations
The retired/deprecated item that is being replaced.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ReplacedIDsType_ReplacedID SDCResources_xsd.tmp#ReplacedIDsType
Type ReplacedIDsType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children ReplacedID
Instance
<Replaces name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <ReplacedID name="" order="" styleClass="" type="" val="">{1,1}</ReplacedID>
</Replaces>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="Replaces" maxOccurs="1" minOccurs="0" type="ReplacedIDsType">
  <xs:annotation>
    <xs:documentation>The retired/deprecated item that is being replaced.</xs:documentation>
  </xs:annotation>
</xs:element>
Element ReplacedIDsType / ReplacedID
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype
Type anyURI_Stype
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:element name="ReplacedID" type="anyURI_Stype">
</xs:element>
Element ChangeLogType / ChangeDate
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTime_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#dateTime_Stype
Type dateTime_Stype
Type hierarchy
Properties
content complex
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="ChangeDate" type="dateTime_Stype">
</xs:element>
Element ChangeLogType / ChangeDescription
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element name="ChangeDescription" type="string_Stype" minOccurs="0"/>
Element ChangeLogType / Editors
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactsType_Contact SDCResources_xsd.tmp#ContactsType
Type ContactsType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children Comment, Contact, Extension, Property
Instance
<Editors name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <Contact name="" order="" styleClass="" type="">{1,unbounded}</Contact>
</Editors>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="Editors" minOccurs="0" type="ContactsType">
</xs:element>
Element ChangeLogType / ChangeTracking
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ChangeTrackingType_ChangeTrackingID SDCResources_xsd.tmp#ChangeTrackingType
Type ChangeTrackingType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children ChangeTrackingID
Instance
<ChangeTracking name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <ChangeTrackingID name="" order="" styleClass="" type="" val="">{1,unbounded}</ChangeTrackingID>
</ChangeTracking>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element minOccurs="0" name="ChangeTracking" type="ChangeTrackingType">
</xs:element>
Element ChangeTrackingType / ChangeTrackingID
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype
Type string_Stype
Type hierarchy
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:element maxOccurs="unbounded" name="ChangeTrackingID" type="string_Stype"/>
Element ChangeType / NewValue
Namespace urn:ihe:qrph:sdc:2016
Annotations
The new value that the targeted item's content is set to.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType
Type DataTypes_SType
Type hierarchy
Properties
content complex
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Instance
<NewValue name="" order="" styleClass="" type="" xmlns="urn:ihe:qrph:sdc:2016">
  <Comment name="" order="" styleClass="" type="" val="">{0,unbounded}</Comment>
  <Extension name="" order="" styleClass="" type="">{0,unbounded}</Extension>
  <Property name="" order="" propClass="" propName="" styleClass="" type="" val="">{0,unbounded}</Property>
  <anyType maxLength="" minLength="" name="" namespace="" order="" schema="" styleClass="" type="">{1,1}</anyType>
  <anyURI name="" order="" styleClass="" type="" val="">{1,1}</anyURI>
  <base64Binary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</base64Binary>
  <boolean name="" order="" styleClass="" type="" val="">{1,1}</boolean>
  <duration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</duration>
  <byte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</byte>
  <date name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</date>
  <dateTimeStamp name="" order="" styleClass="" type="" val="">{1,1}</dateTimeStamp>
  <decimal name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</decimal>
  <dateTime name="" order="" styleClass="" type="" val="">{1,1}</dateTime>
  <double mask="" name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</double>
  <float name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</float>
  <gDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gDay>
  <gMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonth>
  <gMonthDay name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gMonthDay>
  <gYear name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYear>
  <gYearMonth name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</gYearMonth>
  <hexBinary mimeType="" name="" order="" styleClass="" type="" val="">{1,1}</hexBinary>
  <HTML name="" order="" styleClass="" type="">{1,1}</HTML>
  <int name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</int>
  <integer name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</integer>
  <long name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</long>
  <negativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</negativeInteger>
  <nonNegativeInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonNegativeInteger>
  <nonPositiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</nonPositiveInteger>
  <positiveInteger name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</positiveInteger>
  <short name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</short>
  <string name="" order="" styleClass="" type="" val="">{1,1}</string>
  <time name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</time>
  <unsignedByte name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedByte>
  <unsignedInt name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedInt>
  <unsignedLong name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedLong>
  <unsignedShort name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</unsignedShort>
  <XML name="" order="" schema="" styleClass="" type="">{1,1}</XML>
  <yearMonthDuration name="" order="" quantEnum="" styleClass="" type="" val="">{1,1}</yearMonthDuration>
</NewValue>
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:element name="NewValue" type="DataTypes_SType">
  <xs:annotation>
    <xs:documentation>The new value that the targeted item's content is set to.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesNumeric_DEType / byte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#byte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#byte_Stype SDCDataTypes_xsd.tmp#byte_DEtype_minInclusive SDCDataTypes_xsd.tmp#byte_DEtype_maxInclusive SDCDataTypes_xsd.tmp#byte_DEtype_minExclusive SDCDataTypes_xsd.tmp#byte_DEtype_maxExclusive SDCDataTypes_xsd.tmp#byte_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#byte_DEtype
Type byte_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:byte optional
maxInclusive xs:byte optional
minExclusive xs:byte optional
minInclusive xs:byte optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:byte optional
Source
<xs:element name="byte" nillable="true" type="byte_DEtype">
</xs:element>
Element DataTypesNumeric_DEType / decimal
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#decimal_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#decimal_Stype SDCDataTypes_xsd.tmp#decimal_DEtype_minInclusive SDCDataTypes_xsd.tmp#decimal_DEtype_maxInclusive SDCDataTypes_xsd.tmp#decimal_DEtype_minExclusive SDCDataTypes_xsd.tmp#decimal_DEtype_maxExclusive SDCDataTypes_xsd.tmp#decimal_DEtype_fractionDigits SDCDataTypes_xsd.tmp#decimal_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#decimal_DEtype
Type decimal_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:decimal optional
maxInclusive xs:decimal optional
minExclusive xs:decimal optional
minInclusive xs:decimal optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:decimal optional
Source
<xs:element name="decimal" nillable="true" type="decimal_DEtype">
</xs:element>
Element DataTypesNumeric_DEType / double
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#double_Stype_val SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#double_Stype SDCDataTypes_xsd.tmp#double_DEtype_minInclusive SDCDataTypes_xsd.tmp#double_DEtype_maxInclusive SDCDataTypes_xsd.tmp#double_DEtype_minExclusive SDCDataTypes_xsd.tmp#double_DEtype_maxExclusive SDCDataTypes_xsd.tmp#double_DEtype_fractionDigits SDCDataTypes_xsd.tmp#double_DEtype_totalDigits SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#double_DEtype
Type double_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:double optional
maxInclusive xs:double optional
minExclusive xs:double optional
minInclusive xs:double optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:double optional
Source
<xs:element name="double" nillable="true" type="double_DEtype"/>
Element DataTypesNumeric_DEType / float
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#float_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#float_Stype SDCDataTypes_xsd.tmp#float_DEtype_minInclusive SDCDataTypes_xsd.tmp#float_DEtype_maxInclusive SDCDataTypes_xsd.tmp#float_DEtype_minExclusive SDCDataTypes_xsd.tmp#float_DEtype_maxExclusive SDCDataTypes_xsd.tmp#float_DEtype_fractionDigits SDCDataTypes_xsd.tmp#float_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#float_DEtype
Type float_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
fractionDigits xs:unsignedByte optional
mask xs:string optional
maxExclusive xs:float optional
maxInclusive xs:float optional
minExclusive xs:float optional
minInclusive xs:float optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:float optional
Source
<xs:element name="float" nillable="true" type="float_DEtype"/>
Element DataTypesNumeric_DEType / hexBinary
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#hexBinary_Stype_mimeType SDCDataTypes_xsd.tmp#hexBinary_Stype_val SDCDataTypes_xsd.tmp#hexBinary_Stype SDCDataTypes_xsd.tmp#hexBinary_DEtype_minLength SDCDataTypes_xsd.tmp#hexBinary_DEtype_maxLength SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#hexBinary_DEtype
Type hexBinary_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxLength xs:long optional
mimeType xs:string optional
TBD: Must be a valid MIME type - needs
enumeration
minLength xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:hexBinary optional
Source
<xs:element name="hexBinary" nillable="true" type="hexBinary_DEtype"/>
Element DataTypesNumeric_DEType / int
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#int_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#int_Stype SDCDataTypes_xsd.tmp#int_DEtype_minInclusive SDCDataTypes_xsd.tmp#int_DEtype_maxInclusive SDCDataTypes_xsd.tmp#int_DEtype_minExclusive SDCDataTypes_xsd.tmp#int_DEtype_maxExclusive SDCDataTypes_xsd.tmp#int_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#int_DEtype
Type int_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:int optional
maxInclusive xs:int optional
minExclusive xs:int optional
minInclusive xs:int optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:int optional
Source
<xs:element name="int" nillable="true" type="int_DEtype">
</xs:element>
Element DataTypesNumeric_DEType / integer
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#integer_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#integer_Stype SDCDataTypes_xsd.tmp#integer_DEtype_maxExclusive SDCDataTypes_xsd.tmp#integer_DEtype_minExclusive SDCDataTypes_xsd.tmp#integer_DEtype_maxInclusive SDCDataTypes_xsd.tmp#integer_DEtype_minInclusive SDCDataTypes_xsd.tmp#integer_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#integer_DEtype
Type integer_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:integer optional
maxInclusive xs:integer optional
minExclusive xs:integer optional
minInclusive xs:integer optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:integer optional
Source
<xs:element name="integer" nillable="true" type="integer_DEtype">
</xs:element>
Element DataTypesNumeric_DEType / long
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#long_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#long_Stype SDCDataTypes_xsd.tmp#long_DEtype_minInclusive SDCDataTypes_xsd.tmp#long_DEtype_maxInclusive SDCDataTypes_xsd.tmp#long_DEtype_minExclusive SDCDataTypes_xsd.tmp#long_DEtype_maxExclusive SDCDataTypes_xsd.tmp#long_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#long_DEtype
Type long_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:long optional
maxInclusive xs:long optional
minExclusive xs:long optional
minInclusive xs:long optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:long optional
Source
<xs:element name="long" nillable="true" type="long_DEtype">
</xs:element>
Element DataTypesNumeric_DEType / negativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#negativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#negativeInteger_Stype SDCDataTypes_xsd.tmp#negativeInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#negativeInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#negativeInteger_DEtype
Type negativeInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:negativeInteger optional
maxInclusive xs:negativeInteger optional
minExclusive xs:negativeInteger optional
minInclusive xs:negativeInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:negativeInteger optional
Source
<xs:element name="negativeInteger" nillable="true" type="negativeInteger_DEtype"/>
Element DataTypesNumeric_DEType / nonNegativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#nonNegativeInteger_DEtype
Type nonNegativeInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:nonNegativeInteger optional
maxInclusive xs:nonNegativeInteger optional
minExclusive xs:nonNegativeInteger optional
minInclusive xs:nonNegativeInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonNegativeInteger optional
Source
<xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_DEtype"/>
Element DataTypesNumeric_DEType / nonPositiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#nonPositiveInteger_DEtype
Type nonPositiveInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:nonPositiveInteger optional
maxInclusive xs:nonPositiveInteger optional
minExclusive xs:nonPositiveInteger optional
minInclusive xs:nonPositiveInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonPositiveInteger optional
Source
<xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_DEtype"/>
Element DataTypesNumeric_DEType / positiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#positiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#positiveInteger_Stype SDCDataTypes_xsd.tmp#positiveInteger_DEtype_minInclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_maxInclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_minExclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_maxExclusive SDCDataTypes_xsd.tmp#positiveInteger_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#positiveInteger_DEtype
Type positiveInteger_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:positiveInteger optional
maxInclusive xs:positiveInteger optional
minExclusive xs:positiveInteger optional
minInclusive xs:positiveInteger optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:positiveInteger optional
Source
<xs:element name="positiveInteger" nillable="true" type="positiveInteger_DEtype"/>
Element DataTypesNumeric_DEType / short
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#short_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#short_Stype SDCDataTypes_xsd.tmp#short_DEtype_minInclusive SDCDataTypes_xsd.tmp#short_DEtype_maxInclusive SDCDataTypes_xsd.tmp#short_DEtype_minExclusive SDCDataTypes_xsd.tmp#short_DEtype_maxExclusive SDCDataTypes_xsd.tmp#short_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#short_DEtype
Type short_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:short optional
maxInclusive xs:short optional
minExclusive xs:short optional
minInclusive xs:short optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:short optional
Source
<xs:element name="short" nillable="true" type="short_DEtype"/>
Element DataTypesNumeric_DEType / time
Namespace urn:ihe:qrph:sdc:2016
Annotations
**possibly "HH:MM:SS:ms am/pm 12/24"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#time_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#time_Stype SDCDataTypes_xsd.tmp#time_DEtype_minInclusive SDCDataTypes_xsd.tmp#time_DEtype_maxInclusive SDCDataTypes_xsd.tmp#time_DEtype_minExclusive SDCDataTypes_xsd.tmp#time_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#time_DEtype
Type time_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:time optional
maxInclusive xs:time optional
minExclusive xs:time optional
minInclusive xs:time optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:time optional
Source
<xs:element name="time" nillable="true" type="time_DEtype">
  <xs:annotation>
    <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesNumeric_DEType / unsignedByte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedByte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedByte_Stype SDCDataTypes_xsd.tmp#unsignedByte_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedByte_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedByte_DEtype
Type unsignedByte_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedByte optional
maxInclusive xs:unsignedByte optional
minExclusive xs:unsignedByte optional
minInclusive xs:unsignedByte optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedByte optional
Source
<xs:element name="unsignedByte" nillable="true" type="unsignedByte_DEtype"/>
Element DataTypesNumeric_DEType / unsignedInt
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedInt_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedInt_Stype SDCDataTypes_xsd.tmp#unsignedInt_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedInt_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedInt_DEtype
Type unsignedInt_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedInt optional
maxInclusive xs:unsignedInt optional
minExclusive xs:unsignedInt optional
minInclusive xs:unsignedInt optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedInt optional
Source
<xs:element name="unsignedInt" nillable="true" type="unsignedInt_DEtype"/>
Element DataTypesNumeric_DEType / unsignedLong
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedLong_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedLong_Stype SDCDataTypes_xsd.tmp#unsignedLong_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedLong_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedLong_DEtype
Type unsignedLong_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedLong optional
maxInclusive xs:unsignedLong optional
minExclusive xs:unsignedLong optional
minInclusive xs:unsignedLong optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedLong optional
Source
<xs:element name="unsignedLong" nillable="true" type="unsignedLong_DEtype"/>
Element DataTypesNumeric_DEType / unsignedShort
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedShort_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedShort_Stype SDCDataTypes_xsd.tmp#unsignedShort_DEtype_minInclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_maxInclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_minExclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_maxExclusive SDCDataTypes_xsd.tmp#unsignedShort_DEtype_totalDigits SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#unsignedShort_DEtype
Type unsignedShort_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:unsignedShort optional
maxInclusive xs:unsignedShort optional
minExclusive xs:unsignedShort optional
minInclusive xs:unsignedShort optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
totalDigits restriction of xs:unsignedByte optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedShort optional
Source
<xs:element name="unsignedShort" nillable="true" type="unsignedShort_DEtype"/>
Element DataTypesNumeric_DEType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minExclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype
Type yearMonthDuration_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:duration optional
maxInclusive xs:duration optional
minExclusive xs:duration optional
minInclusive xs:duration optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
</xs:element>
Element DataTypesNumeric_SType / byte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#byte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#byte_Stype
Type byte_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:byte optional
Source
<xs:element name="byte" nillable="true" type="byte_Stype">
</xs:element>
Element DataTypesNumeric_SType / decimal
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#decimal_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#decimal_Stype
Type decimal_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:decimal optional
Source
<xs:element name="decimal" nillable="true" type="decimal_Stype">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
</xs:element>
Element DataTypesNumeric_SType / double
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#double_Stype_val SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#double_Stype
Type double_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:double optional
Source
<xs:element name="double" nillable="true" type="double_Stype"/>
Element DataTypesNumeric_SType / float
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#float_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#float_Stype
Type float_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:float optional
Source
<xs:element name="float" nillable="true" type="float_Stype"/>
Element DataTypesNumeric_SType / int
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#int_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#int_Stype
Type int_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:int optional
Source
<xs:element name="int" nillable="true" type="int_Stype">
</xs:element>
Element DataTypesNumeric_SType / integer
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#integer_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#integer_Stype
Type integer_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:integer optional
Source
<xs:element name="integer" nillable="true" type="integer_Stype">
</xs:element>
Element DataTypesNumeric_SType / long
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#long_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#long_Stype
Type long_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:long optional
Source
<xs:element name="long" nillable="true" type="long_Stype"/>
Element DataTypesNumeric_SType / negativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#negativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#negativeInteger_Stype
Type negativeInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:negativeInteger optional
Source
<xs:element name="negativeInteger" nillable="true" type="negativeInteger_Stype"/>
Element DataTypesNumeric_SType / nonNegativeInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonNegativeInteger_Stype
Type nonNegativeInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonNegativeInteger optional
Source
<xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_Stype"/>
Element DataTypesNumeric_SType / nonPositiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#nonPositiveInteger_Stype
Type nonPositiveInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:nonPositiveInteger optional
Source
<xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_Stype"/>
Element DataTypesNumeric_SType / positiveInteger
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#positiveInteger_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#positiveInteger_Stype
Type positiveInteger_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:positiveInteger optional
Source
<xs:element name="positiveInteger" nillable="true" type="positiveInteger_Stype"/>
Element DataTypesNumeric_SType / short
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#short_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#short_Stype
Type short_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:short optional
Source
<xs:element name="short" nillable="true" type="short_Stype"/>
Element DataTypesNumeric_SType / unsignedByte
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedByte_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedByte_Stype
Type unsignedByte_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedByte optional
Source
<xs:element name="unsignedByte" nillable="true" type="unsignedByte_Stype"/>
Element DataTypesNumeric_SType / unsignedInt
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedInt_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedInt_Stype
Type unsignedInt_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedInt optional
Source
<xs:element name="unsignedInt" nillable="true" type="unsignedInt_Stype"/>
Element DataTypesNumeric_SType / unsignedLong
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedLong_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedLong_Stype
Type unsignedLong_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedLong optional
Source
<xs:element name="unsignedLong" nillable="true" type="unsignedLong_Stype"/>
Element DataTypesNumeric_SType / unsignedShort
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#unsignedShort_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#unsignedShort_Stype
Type unsignedShort_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:unsignedShort optional
Source
<xs:element name="unsignedShort" nillable="true" type="unsignedShort_Stype"/>
Element DataTypesNumeric_SType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype
Type yearMonthDuration_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
Element DataTypesDateTime_DEType / dateTime
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

DateTime Data Type 
The dateTime data type is used to specify a date
 and a time. The dateTime is specified in the following form
 "YYYY-MM-DDThh:mm:ss" where: 
 YYYY indicates the year 
 MM indicates the month 
 DD indicates the day 
 T indicates the start of the required time section 
 hh indicates the hour 
 mm indicates the minute 
 ss indicates the second 
 
Time Zones 
 To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time -
 like this: 09:30:10Z 
 or you can specify an offset from the UTC time by adding a positive or negative time behind the
 time - like this: 09:30:10-06:00 or 09:30:10+06:00.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minExclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_maxInclusive SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype_minInclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#dateTimeStamp_DEtype
Type dateTimeStamp_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
mask xs:string optional
maxExclusive xs:dateTime optional
maxInclusive xs:dateTime optional
minExclusive xs:dateTime optional
minInclusive xs:dateTime optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTime" nillable="true" type="dateTimeStamp_DEtype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_DEType / duration
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

Duration Data Type 
The duration data type is used to specify a time interval.
The time interval is specified in the following form
"PnYnMnDTnHnMnS" where: 
 P indicates the period (required) 
 nY indicates the number of years nM indicates the number of months 
 nD indicates the number of days T indicates the start of a time section
 (required if you are going to specify hours, minutes, or seconds) 
 nH indicates the number of hours nM indicates the number of minutes 
 nS indicates the number of seconds 

An element in your document might look like this: P5Y 
 The example above indicates a period of five years. 
 
Or it might look like this: P5Y2M10D. 
 The example above indicates a period of five years, two months, and 10 days. 
 
Or it might look like this: P5Y2M10DT15H. 
 The example above indicates a period of five years, two months, 10 days, and 15 hours. 
 
Or it might look like this: PT15H.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#duration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#duration_Stype SDCDataTypes_xsd.tmp#duration_DEtype_minInclusive SDCDataTypes_xsd.tmp#duration_DEtype_maxInclusive SDCDataTypes_xsd.tmp#duration_DEtype_minExclusive SDCDataTypes_xsd.tmp#duration_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#duration_DEtype
Type duration_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:duration optional
maxInclusive xs:duration optional
minExclusive xs:duration optional
minInclusive xs:duration optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="duration" nillable="true" type="duration_DEtype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_DEType / gMonthDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonthDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonthDay_Stype SDCDataTypes_xsd.tmp#gMonthDay_DEtype_minInclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_minExclusive SDCDataTypes_xsd.tmp#gMonthDay_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gMonthDay_DEtype
Type gMonthDay_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gMonthDay optional
maxInclusive xs:gMonthDay optional
minExclusive xs:gMonthDay optional
minInclusive xs:gMonthDay optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonthDay optional
Source
<xs:element name="gMonthDay" nillable="true" type="gMonthDay_DEtype"/>
Element DataTypesDateTime_DEType / gYear
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gYear_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gYear_Stype SDCDataTypes_xsd.tmp#gYear_DEtype_minInclusive SDCDataTypes_xsd.tmp#gYear_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gYear_DEtype_minExclusive SDCDataTypes_xsd.tmp#gYear_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gYear_DEtype
Type gYear_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gYear optional
maxInclusive xs:gYear optional
minExclusive xs:gYear optional
minInclusive xs:gYear optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gYear optional
Source
<xs:element name="gYear" nillable="true" type="gYear_DEtype"/>
Element DataTypesDateTime_DEType / gYearMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype SDCDataTypes_xsd.tmp#gMonth_DEtype_minInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxInclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_minExclusive SDCDataTypes_xsd.tmp#gMonth_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#gMonth_DEtype
Type gMonth_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:gMonth optional
maxInclusive xs:gMonth optional
minExclusive xs:gMonth optional
minInclusive xs:gMonth optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gYearMonth" nillable="true" type="gMonth_DEtype"/>
Element DataTypesDateTime_DEType / time
Namespace urn:ihe:qrph:sdc:2016
Annotations
**possibly "HH:MM:SS:ms am/pm 12/24"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#time_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#time_Stype SDCDataTypes_xsd.tmp#time_DEtype_minInclusive SDCDataTypes_xsd.tmp#time_DEtype_maxInclusive SDCDataTypes_xsd.tmp#time_DEtype_minExclusive SDCDataTypes_xsd.tmp#time_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#time_DEtype
Type time_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:time optional
maxInclusive xs:time optional
minExclusive xs:time optional
minInclusive xs:time optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:time optional
Source
<xs:element name="time" nillable="true" type="time_DEtype">
  <xs:annotation>
    <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_DEType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxInclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_minExclusive SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype_maxExclusive SDCDataTypes_xsd.tmp#MaskAttributes SDCDataTypes_xsd.tmp#QuantAttributes SDCDataTypes_xsd.tmp#yearMonthDuration_DEtype
Type yearMonthDuration_DEtype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Default Use Annotation
allowAPPROX xs:boolean false optional
allowGT xs:boolean false optional
allowGTE xs:boolean false optional
allowLT xs:boolean false optional
allowLTE xs:boolean false optional
mask xs:string optional
maxExclusive xs:duration optional
maxInclusive xs:duration optional
minExclusive xs:duration optional
minInclusive xs:duration optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
</xs:element>
Element DataTypesDateTime_SType / duration
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

Duration Data Type The duration data type is used to specify a time
 interval. The time interval is specified in the following form:
 "PnYnMnDTnHnMnS" where: 
 P indicates the period (required) 
 nY indicates the number of years nM indicates the number of months 
 nD indicates the number of days T indicates the start of a time section
 (required if you are going to specify hours, minutes, or seconds) 
 nH indicates the number of hours nM indicates the number of minutes 
 nS indicates the number of seconds 
 
An element in your document might look like this: P5Y 
 The example above indicates a period of five years. 
Or it might look like this: P5Y2M10D. 
 The example above indicates a period of five years, two months, and 10 days. 
Or it might look like this: P5Y2M10DT15H. 
 The example above indicates a period of five years, two months, 10 days, and 15 hours. 
Or it might look like this: PT15H.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#duration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#duration_Stype
Type duration_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="duration" nillable="true" type="duration_Stype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form: "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_SType / date
Namespace urn:ihe:qrph:sdc:2016
Annotations
**Does SDC need a list of valid patterns for all date/time types?
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#date_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#date_Stype
Type date_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:date optional
Source
<xs:element name="date" nillable="true" type="date_Stype">
  <xs:annotation>
    <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_SType / dateTimeStamp
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype
Type dateTimeStamp_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_Stype">
  <xs:annotation>
    <xs:documentation>
    </xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_SType / dateTime
Namespace urn:ihe:qrph:sdc:2016
Annotations

http://www.w3schools.com/schema/schema_dtypes_date.asp

DateTime Data Type The dateTime data type is used to specify a date
and a time. 
The dateTime is specified in the following form
"YYYY-MM-DDThh:mm:ss" where: 
YYYY indicates the year 
MM indicates the month 
DD indicates the day 
T indicates the start of the required time section 
hh indicates the hour mm indicates the minute 
ss indicates the second 
 
Time Zones To specify a time zone, you can either enter a time
in UTC time by adding a "Z" behind the time -
like this: 09:30:10Z 
or you can specify an offset from the UTC time 
by adding a positive or negative time behind the
time - like this: 09:30:10-06:00 or 09:30:10+06:00.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#dateTimeStamp_Stype_val SDCDataTypes_xsd.tmp#dateTimeStamp_Stype
Type dateTimeStamp_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:dateTime optional
Source
<xs:element name="dateTime" nillable="true" type="dateTimeStamp_Stype">
  <xs:annotation>
    <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_SType / gDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gDay_Stype
Type gDay_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gDay optional
Source
<xs:element name="gDay" nillable="true" type="gDay_Stype"/>
Element DataTypesDateTime_SType / gMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype
Type gMonth_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gMonth" nillable="true" type="gMonth_Stype"/>
Element DataTypesDateTime_SType / gMonthDay
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonthDay_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonthDay_Stype
Type gMonthDay_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonthDay optional
Source
<xs:element name="gMonthDay" nillable="true" type="gMonthDay_Stype"/>
Element DataTypesDateTime_SType / gYear
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gYear_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gYear_Stype
Type gYear_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gYear optional
Source
<xs:element name="gYear" nillable="true" type="gYear_Stype"/>
Element DataTypesDateTime_SType / gYearMonth
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#gMonth_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#gMonth_Stype
Type gMonth_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:gMonth optional
Source
<xs:element name="gYearMonth" nillable="true" type="gMonth_Stype"/>
Element DataTypesDateTime_SType / time
Namespace urn:ihe:qrph:sdc:2016
Annotations
**possibly "HH:MM:SS:ms am/pm 12/24"
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#time_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#time_Stype
Type time_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:time optional
Source
<xs:element name="time" nillable="true" type="time_Stype">
  <xs:annotation>
    <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
  </xs:annotation>
</xs:element>
Element DataTypesDateTime_SType / yearMonthDuration
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#yearMonthDuration_Stype_val SDCDataTypes_xsd.tmp#quantEnum SDCDataTypes_xsd.tmp#yearMonthDuration_Stype
Type yearMonthDuration_Stype
Type hierarchy
Properties
content complex
nillable true
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
quantEnum restriction of xs:string optional
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:duration optional
Source
<xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
Element DataTypesDateTime_SType / List000
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram
Source
<xs:element name="List000"/>
Complex Type IdentifiedExtensionType
Namespace urn:ihe:qrph:sdc:2016
Annotations
This is the base type for all subtypes that require a unique URI identifier.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#IDAttributes
Type extension of ExtensionBaseType
Type hierarchy
Properties
abstract true
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
ID URI_Atype required
A unique identifier for critical types in FormDesign.
TODO: Needs Schematron to calidate uniqueness in each form.
baseURI URI_Atype optional
If the ID does not use the default base URI (namespace), then the local baseURI goes here. Note that all IDs must be unique within a form, even if they do not have the same baseURI. 

Ideally, the baseURI + ID should combine to form a *globally* unique identifier, that uniquely identifies an item in a particular form.  The same baseURI and ID may be reused in derived or versioned forms, as long as the context stays the same, and any affected data elements remain unchanged in context and semantics.  Following this approach is likely to simplify analytics based on form content.
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType abstract="true" name="IdentifiedExtensionType">
  <xs:annotation>
    <xs:documentation>This is the base type for all subtypes that require a unique URI identifier.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:attributeGroup ref="IDAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ExtensionBaseType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property
Type extension of BaseType
Type hierarchy
Properties
abstract true
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType abstract="true" name="ExtensionBaseType">
  <xs:annotation>
    <xs:documentation/>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Comment" type="CommentType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Extension" type="ExtensionType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Property" type="PropertyType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type PropertyType
Namespace urn:ihe:qrph:sdc:2016
Annotations
MOVED: From SDCFormDesign
CHANGED:
Property is any type of data that is associated with any form item (e.g., section, question, list item) in any context.  The Property context is specified by the @type attribute.  Examples of @type values may include:
-alternate language representations, e.g., 'spanish'
-'instruction'
-'tooltip' 
-'help' for a pop-up help box
-'outlining' (such as question numbering)

The @type enumerations must be defined and documented for the particular use case, and are currently out of scope in this schema definition.  Multiple type tokens for a single element are supported.

RENAMED:  'OtherText' to 'Property' 9/14/2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PropertyType_propName SDCResources_xsd.tmp#PropertyType_propClass SDCResources_xsd.tmp#PropertyType_val SDCResources_xsd.tmp#PropertyType_TypedValue
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property, TypedValue
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
propClass xs:NMTOKENS optional
NEW
propName xs:NMTOKEN required
NEW
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:complexType name="PropertyType">
  <xs:annotation>
    <xs:documentation>MOVED: From SDCFormDesign CHANGED: Property is any type of data that is associated with any form item (e.g., section, question, list item) in any context. The Property context is specified by the @type attribute. Examples of @type values may include: -alternate language representations, e.g., 'spanish' -'instruction' -'tooltip' -'help' for a pop-up help box -'outlining' (such as question numbering) The @type enumerations must be defined and documented for the particular use case, and are currently out of scope in this schema definition. Multiple type tokens for a single element are supported. RENAMED: 'OtherText' to 'Property' 9/14/2016</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="TypedValue" type="DataTypes_SType">
          <xs:annotation>
            <xs:documentation>Contains optional typed data.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute form="unqualified" name="propName" type="xs:NMTOKEN" use="required">
        <xs:annotation>
          <xs:documentation>NEW</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute form="unqualified" name="propClass" type="xs:NMTOKENS">
        <xs:annotation>
          <xs:documentation>NEW</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="val" type="xs:string" use="optional"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypes_SType
Namespace urn:ihe:qrph:sdc:2016
Annotations
MOVED from SDCDataTypes:
SDC datatypes in Simple (S) format, based mostly on W3C specifications.  Uses baseAttributes and Extension capability to enhance the list of Data Types.        **CHECK for ERRORS and completeness**
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypes_SType">
  <xs:annotation>
    <xs:documentation>MOVED from SDCDataTypes: SDC datatypes in Simple (S) format, based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. **CHECK for ERRORS and completeness**</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="anyType" nillable="true" type="anyType_DEtype">
        </xs:element>
        <xs:element name="anyURI" nillable="true" type="anyURI_Stype">
        </xs:element>
        <xs:element name="base64Binary" nillable="true" type="base64Binary_Stype">
          <xs:annotation>
            <xs:documentation>**SDC may need a valid list of MIME types.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="boolean" nillable="true" type="boolean_Stype"/>
        <xs:element name="duration" nillable="true" type="duration_Stype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form: "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="byte" nillable="true" type="byte_Stype">
        </xs:element>
        <xs:element name="date" nillable="true" type="date_Stype">
          <xs:annotation>
            <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_Stype">
          <xs:annotation>
            <xs:documentation>
            </xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="decimal" nillable="true" type="decimal_Stype">
          <xs:annotation>
            <xs:documentation/>
          </xs:annotation>
        </xs:element>
        <xs:element name="dateTime" nillable="true" type="dateTimeStamp_Stype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="double" nillable="true" type="double_Stype"/>
        <xs:element name="float" nillable="true" type="float_Stype"/>
        <xs:element name="gDay" nillable="true" type="gDay_Stype"/>
        <xs:element name="gMonth" nillable="true" type="gMonth_Stype"/>
        <xs:element name="gMonthDay" nillable="true" type="gMonthDay_Stype"/>
        <xs:element name="gYear" nillable="true" type="gYear_Stype"/>
        <xs:element name="gYearMonth" nillable="true" type="gMonth_Stype"/>
        <xs:element name="hexBinary" nillable="true" type="hexBinary_Stype">
          <xs:annotation>
            <xs:documentation>**Does SDC need list of valid MIME types?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="HTML" nillable="true" type="HTML_Stype"/>
        <xs:element name="int" nillable="true" type="int_Stype">
        </xs:element>
        <xs:element name="integer" nillable="true" type="integer_Stype">
        </xs:element>
        <xs:element name="long" nillable="true" type="long_Stype"/>
        <xs:element name="negativeInteger" nillable="true" type="negativeInteger_Stype"/>
        <xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_Stype"/>
        <xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_Stype"/>
        <xs:element name="positiveInteger" nillable="true" type="positiveInteger_Stype"/>
        <xs:element name="short" nillable="true" type="short_Stype"/>
        <xs:element name="string" nillable="true" type="string_Stype"/>
        <xs:element name="time" nillable="true" type="time_Stype">
          <xs:annotation>
            <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="unsignedByte" nillable="true" type="unsignedByte_Stype"/>
        <xs:element name="unsignedInt" nillable="true" type="unsignedInt_Stype"/>
        <xs:element name="unsignedLong" nillable="true" type="unsignedLong_Stype"/>
        <xs:element name="unsignedShort" nillable="true" type="unsignedShort_Stype"/>
        <xs:element name="XML" nillable="true" type="XML_Stype"/>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ItemNameType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Moved from SDCFormDesign
The type is a standard way to point to a named item anywhere in a FormDesign template.  A named item is any element that has the @name attribute set to a unique value.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ItemNameType_itemName
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
itemName xs:NCName required
The @name attribute of the referenced element.
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ItemNameType">
  <xs:annotation>
    <xs:documentation>Moved from SDCFormDesign The type is a standard way to point to a named item anywhere in a FormDesign template. A named item is any element that has the @name attribute set to a unique value.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:attribute name="itemName" type="xs:NCName" use="required">
        <xs:annotation>
          <xs:documentation>The @name attribute of the referenced element.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type CodingType
Namespace urn:ihe:qrph:sdc:2016
Annotations
This type represents any type of coding, terminology, classification, keyword, or local value system that may be applied to any displayable item in a
FormDesign template.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#CodingType_Code SDCResources_xsd.tmp#CodingType_TypedValue SDCResources_xsd.tmp#CodingType_CodeText SDCResources_xsd.tmp#CodingType_CodeMatch SDCResources_xsd.tmp#CodingType_CodeSystem SDCResources_xsd.tmp#CodingType_CodeURI SDCResources_xsd.tmp#CodingType_Units
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Code, CodeMatch, CodeSystem, CodeText, CodeURI, Comment, Extension, Property, TypedValue, Units
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="CodingType">
  <xs:annotation>
    <xs:documentation>This type represents any type of coding, terminology, classification, keyword, or local value system that may be applied to any displayable item in a FormDesign template.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" name="Code" nillable="true" type="string_Stype">
          <xs:annotation>
            <xs:documentation>A standard code, or a local value from a custom coding system, that can be used to consistently identify, or provide a standard value for, the coded item.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="TypedValue" type="DataTypes_SType">
          <xs:annotation>
            <xs:documentation>Data type enumeration derived from W3C XML Schema. If the code is derived from a local value system (e.g., numbered answer choices such as clock positions, tumor grades, or clinical scoring systems), then the data type of the local value may be specified here. This may be important if the code value will need to me manipulated mathematically.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="CodeText" type="RichTextType">
          <xs:annotation>
            <xs:documentation>The human readable text that accompanies the assigned code and represents the code's precise meaning (semantics) or usage.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="CodeMatch" minOccurs="0" type="CodeMatchType">
          <xs:annotation>
            <xs:documentation>Degree of match between the mapped item and the assigned code - @codeMatchType holds an entry from an enumerated list of match types.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="CodeSystem" type="CodeSystemType" minOccurs="0">
        </xs:element>
        <xs:element minOccurs="0" name="CodeURI" type="anyURI_Stype">
          <xs:annotation>
            <xs:documentation>NEW: Web resource that provides information about the code</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Units" type="UnitsType">
          <xs:annotation>
            <xs:documentation/>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type RichTextType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Representation of plain text with an option for HTML-formatting. Contains optional boilerplate metadata to aid programmatic manipulation. HTML formatting is generally contained in CDATA tags to prevent XML parsing and schema errors.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#RichTextType_val SDCResources_xsd.tmp#RichTextType_RichText
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property, RichText
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:complexType name="RichTextType">
  <xs:annotation>
    <xs:documentation>Representation of plain text with an option for HTML-formatting. Contains optional boilerplate metadata to aid programmatic manipulation. HTML formatting is generally contained in CDATA tags to prevent XML parsing and schema errors.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence minOccurs="0">
        <xs:element form="qualified" name="RichText" type="HTML_Stype"/>
      </xs:sequence>
      <xs:attribute name="val" type="xs:string" use="required"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type CodeMatchType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#CodeMatchType_codeMatchEnum SDCResources_xsd.tmp#CodeMatchType_CodingMatchComment
Type extension of BaseType
Type hierarchy
Used by
Model
Children CodingMatchComment
Attributes
QName Type Default Use Annotation
codeMatchEnum restriction of xs:string Exact Code Match optional
The degree of match between the coded item and the assigned code.
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="CodeMatchType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="CodingMatchComment" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Comment about the degree of match between the mapped item and the assigned code.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="codeMatchEnum" default="Exact Code Match">
        <xs:annotation>
          <xs:documentation>The degree of match between the coded item and the assigned code.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Exact Code Match"/>
            <xs:enumeration value="Close Code Match"/>
            <xs:enumeration value="Code Broader Than Item"/>
            <xs:enumeration value="Code Narrower Than Item"/>
            <xs:enumeration value="Item Implements Data Element Exactly"/>
            <xs:enumeration value="Item Derived From Data Element"/>
            <xs:enumeration value="Item Related To Data Element"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type CodeSystemType
Namespace urn:ihe:qrph:sdc:2016
Annotations
This type represents information about the coding system used in CodingType. It may refer to any type of coding, terminology, classification, keyword, or local value system.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#CodeSystemType_CodeSystemName SDCResources_xsd.tmp#CodeSystemType_ReleaseDate SDCResources_xsd.tmp#CodeSystemType_Version SDCResources_xsd.tmp#CodeSystemType_OID SDCResources_xsd.tmp#CodeSystemType_CodeSystemURI
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children CodeSystemName, CodeSystemURI, Comment, Extension, OID, Property, ReleaseDate, Version
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="CodeSystemType">
  <xs:annotation>
    <xs:documentation>This type represents information about the coding system used in CodingType. It may refer to any type of coding, terminology, classification, keyword, or local value system.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="1" name="CodeSystemName" type="string_Stype">
          <xs:annotation>
            <xs:documentation>The name of the coding system, as recommended by the coding system curators, or as recommended by the agency that creates standards for the code map in use.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="ReleaseDate" type="dateTime_Stype">
          <xs:annotation>
            <xs:documentation>The day that the selected version of the coding system was released for general use by the coding system curators.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Version" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Version of the coding system, using the version format defined by the coding system</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="OID" type="string_Stype">
          <xs:annotation>
            <xs:documentation>The ISO object identifier (OID) for the coding system, as found at the HL7 OID Registry: https://www.hl7.org/oid/index.cfm</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="CodeSystemURI" type="anyURI_Stype">
          <xs:annotation>
            <xs:documentation>Web resource that uniquely identifies the coding system</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type UnitsType
Namespace urn:ihe:qrph:sdc:2016
Annotations
UnitsType represents the measurement standard and its abbreviated notation for quantifiable objects, e.g., miles, km, mm, cm, etc. The default system for standard notations is UCUM.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#UnitsType_unitSystem
Type extension of string_Stype
Type hierarchy
Used by
Attributes
QName Type Default Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
unitSystem xs:string UCUM optional
val xs:string optional
Source
<xs:complexType name="UnitsType">
  <xs:annotation>
    <xs:documentation>UnitsType represents the measurement standard and its abbreviated notation for quantifiable objects, e.g., miles, km, mm, cm, etc. The default system for standard notations is UCUM.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="string_Stype">
      <xs:attribute default="UCUM" name="unitSystem" type="xs:string" use="optional"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type LinkType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A hyperlink to an Internet endpoint such as a web page or web service.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#LinkType_LinkText SDCResources_xsd.tmp#LinkType_LinkURI
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, LinkText, LinkURI, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="LinkType">
  <xs:annotation>
    <xs:documentation>A hyperlink to an Internet endpoint such as a web page or web service.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element minOccurs="0" name="LinkText" type="RichTextType">
          <xs:annotation>
            <xs:documentation>A description of the URI link, usually for display purposes.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="1" name="LinkURI" type="anyURI_Stype">
          <xs:annotation>
            <xs:documentation>Link to external information.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type BlobType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Standard structure for including Binary Large Objects (Blobs) in XML
templates. Blobs can handle any type of binary media, such as images, audio, video,
and data streams of any specified format (such as a MIME type).
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#BlobType_mimeType SDCResources_xsd.tmp#BlobType_fileExtension SDCResources_xsd.tmp#BlobType_Description SDCResources_xsd.tmp#BlobType_Hash SDCResources_xsd.tmp#BlobType_BlobURI SDCResources_xsd.tmp#BlobType_BinaryMediaBase64
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children BinaryMediaBase64, BlobURI, Comment, Description, Extension, Hash, Property
Attributes
QName Type Use Annotation
fileExtension xs:string optional
Use a common file extension (e.g., docx) if there is no @MIME_Type available
mimeType xs:string required
TBD: Must be a valid MIME type - needs enumeration
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="BlobType">
  <xs:annotation>
    <xs:documentation>Standard structure for including Binary Large Objects (Blobs) in XML templates. Blobs can handle any type of binary media, such as images, audio, video, and data streams of any specified format (such as a MIME type).</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Description" type="RichTextType"/>
        <xs:element name="Hash" minOccurs="0" type="HashType">
          <xs:annotation>
            <xs:documentation>Binary hash of the blob data</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:choice>
          <xs:element name="BlobURI" type="anyURI_Stype">
            <xs:annotation>
              <xs:documentation>This URI should contain a URL or web service link to the Blob. It is used instead of incorporating the Blob directly into XML templates.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="BinaryMediaBase64" type="base64Binary_Stype">
            <xs:annotation>
              <xs:documentation>Binary represeentation of the Blob data, encoded using a Base 64 transformation from the original source binary data. Base 64 encoding uses 64 character alphanumeric text (characters A–Z, a–z, 0–9, =, /) to represent the binary data, so that it may be transmitted as "text" inside an XML instance document without the need for escape characters.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:choice>
      </xs:sequence>
      <xs:attribute name="mimeType" type="xs:string" use="required">
        <xs:annotation>
          <xs:documentation>TBD: Must be a valid MIME type - needs enumeration</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="fileExtension" type="xs:string" use="optional">
        <xs:annotation>
          <xs:documentation>Use a common file extension (e.g., docx) if there is no @MIME_Type available</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type HashType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#base64Binary_Stype_mimeType SDCDataTypes_xsd.tmp#base64Binary_Stype_val SDCDataTypes_xsd.tmp#base64Binary_Stype SDCResources_xsd.tmp#HashType_hashAlgorithm
Type extension of base64Binary_Stype
Type hierarchy
Used by
Element BlobType/Hash
Attributes
QName Type Use Annotation
hashAlgorithm xs:string optional
mimeType xs:string optional
TBD: Must be a valid MIME type
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:base64Binary optional
Source
<xs:complexType name="HashType">
  <xs:complexContent>
    <xs:extension base="base64Binary_Stype">
      <xs:attribute name="hashAlgorithm" type="xs:string"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ContactType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A model structure for a Person or Organization that generally performs a particular stated role.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactType_Person SDCResources_xsd.tmp#ContactType_Organization
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Organization, Person, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ContactType">
  <xs:annotation>
    <xs:documentation>A model structure for a Person or Organization that generally performs a particular stated role.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="Person" type="PersonType"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type PersonType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A model structure for a Person object.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PersonType_PersonName SDCResources_xsd.tmp#PersonType_AliasName SDCResources_xsd.tmp#PersonType_Job SDCResources_xsd.tmp#PersonType_StreetAddress SDCResources_xsd.tmp#PersonType_Email SDCResources_xsd.tmp#PersonType_Phone SDCResources_xsd.tmp#PersonType_WebURL SDCResources_xsd.tmp#PersonType_Role SDCResources_xsd.tmp#PersonType_Identifier SDCResources_xsd.tmp#PersonType_Usage
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children AliasName, Comment, Email, Extension, Identifier, Job, PersonName, Phone, Property, Role, StreetAddress, Usage, WebURL
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="PersonType">
  <xs:annotation>
    <xs:documentation>A model structure for a Person object.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="1" name="PersonName" type="NameType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="AliasName" type="NameType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Job" type="JobType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="StreetAddress" type="AddressType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Email" type="EmailType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Phone" type="PhoneType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="WebURL" type="anyURI_Stype">
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Role" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Role of the person, e.g., creator, copyright holder, accreditor, certifier, curator, etc.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Identifier" type="IdentifierType" maxOccurs="unbounded" minOccurs="0"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
          <xs:annotation>
            <xs:documentation>When this person should be contacted.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type NameType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Structure to define a person's name, including prefixes, suffixes, and degrees.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#NameType_NamePrefix SDCResources_xsd.tmp#NameType_FirstName SDCResources_xsd.tmp#NameType_MiddleName SDCResources_xsd.tmp#NameType_LastName SDCResources_xsd.tmp#NameType_NameSuffix SDCResources_xsd.tmp#NameType_DegreeCert SDCResources_xsd.tmp#NameType_Title
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, DegreeCert, Extension, FirstName, LastName, MiddleName, NamePrefix, NameSuffix, Property, Title
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="NameType">
  <xs:annotation>
    <xs:documentation>Structure to define a person's name, including prefixes, suffixes, and degrees.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element name="NamePrefix" type="string_Stype" minOccurs="0"/>
        <xs:element name="FirstName" type="string_Stype" nillable="true"/>
        <xs:element name="MiddleName" type="string_Stype" minOccurs="0"/>
        <xs:element name="LastName" type="string_Stype" nillable="true"/>
        <xs:element name="NameSuffix" type="string_Stype" minOccurs="0"/>
        <xs:element name="DegreeCert" type="string_Stype" maxOccurs="unbounded" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Acronyms for degrees and certifications, e.g., MD, PhD, FACP (repeat element for each acronym)</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Title" type="string_Stype" minOccurs="0"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type JobType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#JobType_JobTitle SDCResources_xsd.tmp#JobType_Organization SDCResources_xsd.tmp#JobType_StartDate SDCResources_xsd.tmp#JobType_StopDate SDCResources_xsd.tmp#JobType_Description
Type extension of ExtensionBaseType
Type hierarchy
Used by
Element PersonType/Job
Model
Children Comment, Description, Extension, JobTitle, Organization, Property, StartDate, StopDate
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="JobType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="JobTitle" type="string_Stype"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
        <xs:element minOccurs="0" name="StartDate" type="date_Stype"/>
        <xs:element minOccurs="0" name="StopDate" type="date_Stype"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Description" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Job Description</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type OrganizationType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A model structure for an Organization object.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#OrganizationType_OrgName SDCResources_xsd.tmp#OrganizationType_Department SDCResources_xsd.tmp#OrganizationType_StreetAddress SDCResources_xsd.tmp#OrganizationType_Email SDCResources_xsd.tmp#OrganizationType_Phone SDCResources_xsd.tmp#OrganizationType_WebURL SDCResources_xsd.tmp#OrganizationType_Role SDCResources_xsd.tmp#OrganizationType_ContactPerson SDCResources_xsd.tmp#OrganizationType_Identifier SDCResources_xsd.tmp#OrganizationType_Usage
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, ContactPerson, Department, Email, Extension, Identifier, OrgName, Phone, Property, Role, StreetAddress, Usage, WebURL
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="OrganizationType">
  <xs:annotation>
    <xs:documentation>A model structure for an Organization object.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="1" name="OrgName" type="string_Stype" nillable="true"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Department" type="string_Stype"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="StreetAddress" type="AddressType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Email" type="EmailType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Phone" type="PhoneType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="WebURL" type="anyURI_Stype">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Role" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Role of the organization, e.g., creator, copyright holder, accreditor, certifier, curator, etc.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="ContactPerson" type="PersonType"/>
        <xs:element name="Identifier" type="IdentifierType" maxOccurs="unbounded" minOccurs="0"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
          <xs:annotation>
            <xs:documentation>When this organization should be contacted.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type AddressType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A structure for recording street/mailing addresses.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#AddressType_AddressType SDCResources_xsd.tmp#AddressType_InternalAddress SDCResources_xsd.tmp#AddressType_AddressLine SDCResources_xsd.tmp#AddressType_City SDCResources_xsd.tmp#AddressType_Jurisdiction SDCResources_xsd.tmp#AddressType_State SDCResources_xsd.tmp#AddressType_PostalCode SDCResources_xsd.tmp#AddressType_Country SDCResources_xsd.tmp#AddressType_Usage
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children AddressLine, AddressType, City, Comment, Country, Extension, InternalAddress, Jurisdiction, PostalCode, Property, State, Usage
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="AddressType">
  <xs:annotation>
    <xs:documentation>A structure for recording street/mailing addresses.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="AddressType" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Type of address, e.g., home, office, etc</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="10" minOccurs="0" name="InternalAddress" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Address instructions for directing mail within an organizations buildings or corporate infrastructure.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="10" minOccurs="0" name="AddressLine" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Address instructions for directing mail to a street address.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="City" type="string_Stype"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Jurisdiction" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Other optional locale identifier.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="State" type="string_Stype">
          <xs:annotation>
            <xs:documentation>State, Province, etc.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="PostalCode" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Local postal code, e.g., zip code.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Country" type="string_Stype">
          <xs:annotation>
            <xs:documentation>**Need list of official country codes or text?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
          <xs:annotation>
            <xs:documentation>When this address should be used</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type EmailType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A structure for recording email addresses.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#EmailType_EmailAddress SDCResources_xsd.tmp#EmailType_EmailClass SDCResources_xsd.tmp#EmailType_Usage
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, EmailAddress, EmailClass, Extension, Property, Usage
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="EmailType">
  <xs:annotation>
    <xs:documentation>A structure for recording email addresses.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="1" name="EmailAddress" type="EmailAddressType">
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="EmailClass" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Type of email, e.g., home, office, etc</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
          <xs:annotation>
            <xs:documentation>When this email should be used</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type EmailAddressType
Namespace urn:ihe:qrph:sdc:2016
Annotations
***Changed from BaseType to ExtensionBaseType
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#EmailAddressType_val
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val EmailAddress_Stype required
Source
<xs:complexType name="EmailAddressType">
  <xs:annotation>
    <xs:documentation>***Changed from BaseType to ExtensionBaseType</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:attribute name="val" use="required" type="EmailAddress_Stype">
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Simple Type EmailAddress_Stype
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram
Type restriction of xs:string
Facets
pattern [a-zA-Z0-9_\-\.\+-]+@[a-zA-Z0-9\-]+\.[a-zA-Z0-9_\-\.]+
Used by
Source
<xs:simpleType name="EmailAddress_Stype">
  <xs:restriction base="xs:string">
    <xs:pattern value="[a-zA-Z0-9_\-\.\+-]+@[a-zA-Z0-9\-]+\.[a-zA-Z0-9_\-\.]+"/>
  </xs:restriction>
</xs:simpleType>
Complex Type PhoneType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A structure for recording telephone numbers.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PhoneType_PhoneType SDCResources_xsd.tmp#PhoneType_CountryCode SDCResources_xsd.tmp#PhoneType_AreaCode SDCResources_xsd.tmp#PhoneType_PhoneNumber SDCResources_xsd.tmp#PhoneType_PhoneExtension SDCResources_xsd.tmp#PhoneType_Usage
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children AreaCode, Comment, CountryCode, Extension, PhoneExtension, PhoneNumber, PhoneType, Property, Usage
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="PhoneType">
  <xs:annotation>
    <xs:documentation>A structure for recording telephone numbers.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="PhoneType" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Usage type of phone number, e.g., home, office, etc</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="CountryCode" type="CountryCodeType">
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="AreaCode" type="AreaCodeType">
        </xs:element>
        <xs:element name="PhoneNumber" type="PhoneNumberType">
        </xs:element>
        <xs:element maxOccurs="1" minOccurs="0" name="PhoneExtension" type="string_Stype"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Usage" type="string_Stype">
          <xs:annotation>
            <xs:documentation>When this phone number should be used</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type CountryCodeType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#CountryCodeType_val
Type extension of BaseType
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val CountryCode_Stype required
Source
<xs:complexType name="CountryCodeType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:attribute name="val" use="required" type="CountryCode_Stype">
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Simple Type CountryCode_Stype
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram
Type restriction of xs:unsignedByte
Facets
maxInclusive 99
Used by
Source
<xs:simpleType name="CountryCode_Stype">
  <xs:restriction base="xs:unsignedByte">
    <xs:maxInclusive value="99"/>
  </xs:restriction>
</xs:simpleType>
Complex Type AreaCodeType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#AreaCodeType_val
Type extension of BaseType
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val AreaCode_Stype optional
Source
<xs:complexType name="AreaCodeType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:attribute name="val" use="optional" type="AreaCode_Stype">
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Simple Type AreaCode_Stype
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram
Type restriction of xs:unsignedShort
Facets
maxInclusive 999
Used by
Attribute AreaCodeType/@val
Source
<xs:simpleType name="AreaCode_Stype">
  <xs:restriction base="xs:unsignedShort">
    <xs:maxInclusive value="999"/>
  </xs:restriction>
</xs:simpleType>
Complex Type PhoneNumberType
Namespace urn:ihe:qrph:sdc:2016
Annotations
***Changed from BaseType to ExtensionBaseType
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#PhoneNumberType_val
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val PhoneNumber_Stype required
Source
<xs:complexType name="PhoneNumberType">
  <xs:annotation>
    <xs:documentation>***Changed from BaseType to ExtensionBaseType</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:attribute name="val" use="required" type="PhoneNumber_Stype">
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Simple Type PhoneNumber_Stype
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram
Type restriction of xs:string
Facets
pattern \+?\(?\d{2,4}\)?[\d\s-]{3,}
Used by
Source
<xs:simpleType name="PhoneNumber_Stype">
  <xs:restriction base="xs:string">
    <xs:pattern value="\+?\(?\d{2,4}\)?[\d\s-]{3,}"/>
  </xs:restriction>
</xs:simpleType>
Complex Type IdentifierType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A code or id that identifies a person or organization or object according to a standard system such as CLIA or NPI. The system should be specified in the @system attribute.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#IdentifierType_system SDCResources_xsd.tmp#IdentifierType_val
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
system xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string required
Source
<xs:complexType name="IdentifierType">
  <xs:annotation>
    <xs:documentation>A code or id that identifies a person or organization or object according to a standard system such as CLIA or NPI. The system should be specified in the @system attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:attribute name="system" type="xs:string"/>
      <xs:attribute name="val" type="xs:string" use="required"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ItemNameAttributeType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Moved from SDCFormDesign
The type is a standard way to point to a named item anywhere in a FormDesign template.  A named item is any element that has the @name attribute set to a unique value.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ItemNameType_itemName SDCResources_xsd.tmp#ItemNameType SDCResources_xsd.tmp#ItemNameAttributeType_attributeName
Type extension of ItemNameType
Type hierarchy
Used by
Model
Children Comment, Extension, Property
Attributes
QName Type Default Use Annotation
attributeName xs:NCName val optional
itemName xs:NCName required
The @name attribute of the referenced element.
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ItemNameAttributeType">
  <xs:annotation>
    <xs:documentation>Moved from SDCFormDesign The type is a standard way to point to a named item anywhere in a FormDesign template. A named item is any element that has the @name attribute set to a unique value.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ItemNameType">
      <xs:attribute default="val" name="attributeName" type="xs:NCName"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypes_DEType
Namespace urn:ihe:qrph:sdc:2016
Annotations
MOVED from SDCDataTypes:
SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes  and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_DEType_anyType SDCResources_xsd.tmp#DataTypes_DEType_anyURI SDCResources_xsd.tmp#DataTypes_DEType_base64Binary SDCResources_xsd.tmp#DataTypes_DEType_boolean SDCResources_xsd.tmp#DataTypes_DEType_duration SDCResources_xsd.tmp#DataTypes_DEType_byte SDCResources_xsd.tmp#DataTypes_DEType_date SDCResources_xsd.tmp#DataTypes_DEType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_DEType_decimal SDCResources_xsd.tmp#DataTypes_DEType_dateTime SDCResources_xsd.tmp#DataTypes_DEType_double SDCResources_xsd.tmp#DataTypes_DEType_float SDCResources_xsd.tmp#DataTypes_DEType_gDay SDCResources_xsd.tmp#DataTypes_DEType_gMonth SDCResources_xsd.tmp#DataTypes_DEType_gMonthDay SDCResources_xsd.tmp#DataTypes_DEType_gYear SDCResources_xsd.tmp#DataTypes_DEType_gYearMonth SDCResources_xsd.tmp#DataTypes_DEType_hexBinary SDCResources_xsd.tmp#DataTypes_DEType_HTML SDCResources_xsd.tmp#DataTypes_DEType_int SDCResources_xsd.tmp#DataTypes_DEType_integer SDCResources_xsd.tmp#DataTypes_DEType_long SDCResources_xsd.tmp#DataTypes_DEType_negativeInteger SDCResources_xsd.tmp#DataTypes_DEType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_DEType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_DEType_positiveInteger SDCResources_xsd.tmp#DataTypes_DEType_short SDCResources_xsd.tmp#DataTypes_DEType_string SDCResources_xsd.tmp#DataTypes_DEType_time SDCResources_xsd.tmp#DataTypes_DEType_unsignedByte SDCResources_xsd.tmp#DataTypes_DEType_unsignedInt SDCResources_xsd.tmp#DataTypes_DEType_unsignedLong SDCResources_xsd.tmp#DataTypes_DEType_unsignedShort SDCResources_xsd.tmp#DataTypes_DEType_XML SDCResources_xsd.tmp#DataTypes_DEType_yearMonthDuration
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypes_DEType">
  <xs:annotation>
    <xs:documentation>MOVED from SDCDataTypes: SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="anyType" nillable="true" type="anyType_DEtype">
        </xs:element>
        <xs:element name="anyURI" nillable="true" type="anyURI_DEtype">
        </xs:element>
        <xs:element name="base64Binary" nillable="true" type="base64Binary_DEtype">
          <xs:annotation>
            <xs:documentation>**SDC may need a valid list of MIME types.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="boolean" nillable="true" type="boolean_DEtype">
        </xs:element>
        <xs:element name="duration" nillable="true" type="duration_DEtype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="byte" nillable="true" type="byte_DEtype">
        </xs:element>
        <xs:element name="date" nillable="true" type="date_DEtype">
          <xs:annotation>
            <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_DEtype">
        </xs:element>
        <xs:element name="decimal" nillable="true" type="decimal_DEtype">
        </xs:element>
        <xs:element name="dateTime" nillable="true" type="dateTimeStamp_DEtype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="double" nillable="true" type="double_DEtype"/>
        <xs:element name="float" nillable="true" type="float_DEtype"/>
        <xs:element name="gDay" nillable="true" type="gDay_DEtype"/>
        <xs:element name="gMonth" nillable="true" type="gMonth_DEtype"/>
        <xs:element name="gMonthDay" nillable="true" type="gMonthDay_DEtype"/>
        <xs:element name="gYear" nillable="true" type="gYear_DEtype"/>
        <xs:element name="gYearMonth" nillable="true" type="gMonth_DEtype"/>
        <xs:element name="hexBinary" nillable="true" type="hexBinary_DEtype"/>
        <xs:element name="HTML" nillable="true" type="HTML_DEtype">
        </xs:element>
        <xs:element name="int" nillable="true" type="int_DEtype">
        </xs:element>
        <xs:element name="integer" nillable="true" type="integer_DEtype">
        </xs:element>
        <xs:element name="long" nillable="true" type="long_DEtype">
        </xs:element>
        <xs:element name="negativeInteger" nillable="true" type="negativeInteger_DEtype"/>
        <xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_DEtype"/>
        <xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_DEtype"/>
        <xs:element name="positiveInteger" nillable="true" type="positiveInteger_DEtype"/>
        <xs:element name="short" nillable="true" type="short_DEtype"/>
        <xs:element name="string" nillable="true" type="string_DEtype"/>
        <xs:element name="time" nillable="true" type="time_DEtype">
          <xs:annotation>
            <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="unsignedByte" nillable="true" type="unsignedByte_DEtype"/>
        <xs:element name="unsignedInt" nillable="true" type="unsignedInt_DEtype"/>
        <xs:element name="unsignedLong" nillable="true" type="unsignedLong_DEtype"/>
        <xs:element name="unsignedShort" nillable="true" type="unsignedShort_DEtype"/>
        <xs:element name="XML" nillable="true" type="XML_DEtype"/>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
        </xs:element>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type FileType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Information about a file, usually thought of as a binary byte stream
stored on disk. A FileType can also represent a "virtual" file, such as an XML
module in a larger XML document. Such a virtual file could theoretically be stored
as a byte stream, as an independant file on disk or as a database record or set of
records, even if this byte stream is never actually persisted as an independant disk
file.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileType_FileID SDCResources_xsd.tmp#FileType_FileURI SDCResources_xsd.tmp#FileType_DisplayName SDCResources_xsd.tmp#FileType_Title SDCResources_xsd.tmp#FileType_Version SDCResources_xsd.tmp#FileType_FileName SDCResources_xsd.tmp#FileType_FileExtension SDCResources_xsd.tmp#FileType_FileClass SDCResources_xsd.tmp#FileType_FileSizeKB SDCResources_xsd.tmp#FileType_Description SDCResources_xsd.tmp#FileType_Copyright SDCResources_xsd.tmp#FileType_TermsofUse SDCResources_xsd.tmp#FileType_Usage SDCResources_xsd.tmp#FileType_Dates SDCResources_xsd.tmp#FileType_Contacts SDCResources_xsd.tmp#FileType_Approval SDCResources_xsd.tmp#FileType_FileHash SDCResources_xsd.tmp#FileType_Language SDCResources_xsd.tmp#FileType_AssociatedFiles SDCResources_xsd.tmp#FileType_Provenance SDCResources_xsd.tmp#FileType_DefaultSubmissionRule SDCResources_xsd.tmp#FileType_DefaultComplianceRule
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Approval, AssociatedFiles, Comment, Contacts, Copyright, Dates, DefaultComplianceRule, DefaultSubmissionRule, Description, DisplayName, Extension, FileClass, FileExtension, FileHash, FileID, FileName, FileSizeKB, FileURI, Language, Property, Provenance, TermsofUse, Title, Usage, Version
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="FileType">
  <xs:annotation>
    <xs:documentation>Information about a file, usually thought of as a binary byte stream stored on disk. A FileType can also represent a "virtual" file, such as an XML module in a larger XML document. Such a virtual file could theoretically be stored as a byte stream, as an independant file on disk or as a database record or set of records, even if this byte stream is never actually persisted as an independant disk file.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element minOccurs="0" name="FileID" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Internal/local File ID, not necessarily in the format of the FileURI used for all SDC FormDesign items.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="1" name="FileURI" type="anyURI_Stype"/>
        <xs:element name="DisplayName" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Text to be displayed that encapulates the file contents. This may be the same as the internal Title of the file.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Title" type="string_Stype" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Official title of the file.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Version" type="VersionType">
          <xs:annotation>
            <xs:documentation>File version</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="FileName" type="string_Stype">
          <xs:annotation>
            <xs:documentation>The name of the file as saved on disk or other persistant storage.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="FileExtension" type="string_Stype">
          <xs:annotation>
            <xs:documentation>The file type extension that describes the file's internal format. This is usually the 3-4 character text that appears after the last period in the file name, e.g., txt, docx, etc.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="FileClass" type="string_Stype">
          <xs:annotation>
            <xs:documentation>A short description of the class of file, such as "FormDesign XML"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="FileSizeKB" type="positiveInteger_Stype">
        </xs:element>
        <xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Any additional information about the template or file. The type of information should be specified in the @type attribute.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Copyright" type="string_Stype"/>
        <xs:element minOccurs="0" name="TermsofUse" type="string_Stype"/>
        <xs:element minOccurs="0" name="Usage" type="FileUsageType">
          <xs:annotation>
            <xs:documentation>Guidance for when this file should be used, and when it should not be used.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Dates" type="FileDatesType">
          <xs:annotation>
            <xs:documentation>Various dates associated with the file release, versioning and usage.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Contacts" type="ContactsType">
          <xs:annotation>
            <xs:documentation>People and Organizations associated with the file. Specify the type of Contact in the @type attribute. Examples of @type include Curator, Author, and Authority.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Approval" maxOccurs="unbounded" type="ApprovalType">
          <xs:annotation>
            <xs:documentation>Documentation of review and acceptance of the file for production usage.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="FileHash" type="FileHashType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Language" type="LanguageType"/>
        <xs:element minOccurs="0" name="AssociatedFiles" type="AssociatedFilesType">
          <xs:annotation>
            <xs:documentation>Link to any associated files, such as schemas, reference documents, manuals, etc.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element minOccurs="0" name="Provenance" type="ProvenanceType">
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="DefaultSubmissionRule" type="SubmissionRuleType"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="DefaultComplianceRule" type="ComplianceRuleType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type VersionType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A generic structure for recording file version metadata.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#versionAttributes SDCResources_xsd.tmp#VersionType_VersioningReference SDCResources_xsd.tmp#VersionType_VersionComments SDCResources_xsd.tmp#VersionType_Changes
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Changes, Comment, Extension, Property, VersionComments, VersioningReference
Attributes
QName Type Use Annotation
fullVersion xs:string required
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
versionLevel.1 xs:string optional
Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.
versionLevel.2 xs:string optional
versionLevel.3 xs:string optional
versionLevel.4 xs:string optional
versionLevel.5 xs:string optional
versionRegExPattern xs:string required
Regular Expression that determines the format of the Full Version
Source
<xs:complexType name="VersionType">
  <xs:annotation>
    <xs:documentation>A generic structure for recording file version metadata.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element name="VersioningReference" type="FileType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Information about the document that describes the versioning methodology nomenclature.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="VersionComments" type="RichTextType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Comments about the changes in this version</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Changes" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Itemized list of changes in the new version</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:complexContent>
              <xs:extension base="ExtensionBaseType">
                <xs:sequence>
                  <xs:element name="Change" type="ChangeLogType" maxOccurs="unbounded"/>
                </xs:sequence>
              </xs:extension>
            </xs:complexContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
      <xs:attributeGroup ref="versionAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type FileUsageType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileUsageType_Included SDCResources_xsd.tmp#FileUsageType_Excluded SDCResources_xsd.tmp#FileUsageType_Description
Type extension of ExtensionBaseType
Type hierarchy
Used by
Element FileType/Usage
Model
Children Comment, Description, Excluded, Extension, Included, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="FileUsageType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence minOccurs="0">
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Included" type="CodingType">
          <xs:annotation>
            <xs:documentation>Reasons to use the file</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="Excluded" type="CodingType">
          <xs:annotation>
            <xs:documentation>Reasons to not use the file</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Non-coded text describing usage criteria.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type FileDatesType
Namespace urn:ihe:qrph:sdc:2016
Annotations
List of standard kinds of dates that may apply to a file or its usage.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#FileDatesType_FileDate SDCResources_xsd.tmp#FileDatesType_PreviousRevisionDate SDCResources_xsd.tmp#FileDatesType_ReleaseDate SDCResources_xsd.tmp#FileDatesType_EffectiveDate SDCResources_xsd.tmp#FileDatesType_FirstReleaseDate SDCResources_xsd.tmp#FileDatesType_UsageStartDate SDCResources_xsd.tmp#FileDatesType_RetirementDate SDCResources_xsd.tmp#FileDatesType_OtherDate
Type extension of ExtensionBaseType
Type hierarchy
Used by
Element FileType/Dates
Model
Children Comment, EffectiveDate, Extension, FileDate, FirstReleaseDate, OtherDate, PreviousRevisionDate, Property, ReleaseDate, RetirementDate, UsageStartDate
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="FileDatesType">
  <xs:annotation>
    <xs:documentation>List of standard kinds of dates that may apply to a file or its usage.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element minOccurs="0" name="FileDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="PreviousRevisionDate" maxOccurs="unbounded" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="ReleaseDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="EffectiveDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="FirstReleaseDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="UsageStartDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="RetirementDate" type="dateTime_Stype">
        </xs:element>
        <xs:element minOccurs="0" name="OtherDate" maxOccurs="unbounded" type="dateTime_Stype">
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ContactsType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ContactsType_Contact
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Contact, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ContactsType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" name="Contact" type="ContactType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ApprovalType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ApprovalType_ApprovalContact SDCResources_xsd.tmp#ApprovalType_Description
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children ApprovalContact, Comment, Description, Extension, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ApprovalType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence minOccurs="0">
        <xs:element maxOccurs="unbounded" name="ApprovalContact" type="ContactType" minOccurs="0"/>
        <xs:element maxOccurs="unbounded" name="Description" nillable="false" minOccurs="0" type="string_Stype">
          <xs:annotation>
            <xs:documentation>Non-structured text describing file approval.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type FileHashType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#FileHashType_hashType
Type extension of string_Stype
Type hierarchy
Used by
Attributes
QName Type Use Annotation
hashType xs:string optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:complexType name="FileHashType">
  <xs:complexContent>
    <xs:extension base="string_Stype">
      <xs:attribute name="hashType" type="xs:string"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type LanguageType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A generic structure for recording languages.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#LanguageType_Language SDCResources_xsd.tmp#LanguageType_LanguageCode.ISO.639.3
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Language, LanguageCode.ISO.639.3, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="LanguageType">
  <!-- The original form of this type (from ISO 19763-10 and 11179-3) is far too complex for SDC needs. -->
  <xs:annotation>
    <xs:documentation>A generic structure for recording languages.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="0" name="Language" type="string_Stype">
          <xs:annotation>
            <xs:documentation>The language used for text in SDC templates.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="LanguageCode.ISO.639.3" type="LanguageCode.ISO.639.3_Type">
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type LanguageCode.ISO.639.3_Type
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#LanguageCode.ISO.639.3_Type_val
Type restriction of string_Stype
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val LanguageCode.ISO.639.3_StypeEnum required
Source
<xs:complexType name="LanguageCode.ISO.639.3_Type">
  <xs:complexContent>
    <xs:restriction base="string_Stype">
      <xs:attribute name="val" use="required" type="LanguageCode.ISO.639.3_StypeEnum">
      </xs:attribute>
    </xs:restriction>
  </xs:complexContent>
</xs:complexType>
Simple Type LanguageCode.ISO.639.3_StypeEnum
Namespace urn:ihe:qrph:sdc:2016
Annotations
Based on ISO-639-3 Language Codes. See:
https://en.wikipedia.org/wiki/ISO_639:e
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration eng
enumeration esp
enumeration fra
Used by
Source
<xs:simpleType name="LanguageCode.ISO.639.3_StypeEnum">
  <xs:annotation>
    <xs:documentation>Based on ISO-639-3 Language Codes. See: https://en.wikipedia.org/wiki/ISO_639:e</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="eng"/>
    <xs:enumeration value="esp"/>
    <xs:enumeration value="fra"/>
  </xs:restriction>
</xs:simpleType>
Complex Type AssociatedFilesType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#AssociatedFilesType_File
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, File, Property
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="AssociatedFilesType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element name="File" type="FileType" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ProvenanceType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ProvenanceType_ReplacedFile
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property, ReplacedFile
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ProvenanceType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element name="ReplacedFile" type="FileType" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type SubmissionRuleType
Namespace urn:ihe:qrph:sdc:2016
Annotations
information about where to submit a completed form
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#SubmissionRuleType_formID SDCResources_xsd.tmp#SubmissionRuleType_ruleID SDCResources_xsd.tmp#SubmissionRuleType_Destination SDCResources_xsd.tmp#SubmissionRuleType_RuleDescription
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Destination, Extension, Property, RuleDescription
Attributes
QName Type Use Annotation
formID URI_Atype optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
ruleID URI_Atype required
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="SubmissionRuleType">
  <xs:annotation>
    <xs:documentation>information about where to submit a completed form</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" minOccurs="1" name="Destination" type="DestinationType">
        </xs:element>
        <xs:element minOccurs="0" name="RuleDescription" type="string_Stype"/>
      </xs:sequence>
      <xs:attribute name="formID" type="URI_Atype"/>
      <xs:attribute name="ruleID" type="URI_Atype" use="required"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DestinationType
Namespace urn:ihe:qrph:sdc:2016
Annotations
***Changed from BaseType to ExtensionBaseType
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DestinationType_Endpoint SDCResources_xsd.tmp#DestinationType_EndpointDescription SDCResources_xsd.tmp#DestinationType_SubmissionTechnology SDCResources_xsd.tmp#DestinationType_Organization
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Endpoint, EndpointDescription, Extension, Organization, Property, SubmissionTechnology
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DestinationType">
  <xs:annotation>
    <xs:documentation>***Changed from BaseType to ExtensionBaseType</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence maxOccurs="1">
        <xs:element maxOccurs="1" minOccurs="1" name="Endpoint" type="anyURI_Stype"/>
        <xs:element maxOccurs="1" minOccurs="1" name="EndpointDescription" type="string_Stype"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="SubmissionTechnology" type="string_Stype"/>
        <xs:element maxOccurs="1" minOccurs="0" name="Organization" type="OrganizationType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ComplianceRuleType
Namespace urn:ihe:qrph:sdc:2016
Annotations
General information about how information in a particular form package must be handled. This may include, e.g., security, completeness, transmission, and validation criteria.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ComplianceRuleType_ruleID SDCResources_xsd.tmp#ComplianceRuleType_formID SDCResources_xsd.tmp#ComplianceRuleType_Description SDCResources_xsd.tmp#ComplianceRuleType_ComplianceOrganization
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, ComplianceOrganization, Description, Extension, Property
Attributes
QName Type Use Annotation
formID URI_Atype optional
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
ruleID URI_Atype required
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ComplianceRuleType">
  <xs:annotation>
    <xs:documentation>General information about how information in a particular form package must be handled. This may include, e.g., security, completeness, transmission, and validation criteria.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element maxOccurs="1" minOccurs="1" name="Description" type="string_Stype"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="ComplianceOrganization" type="OrganizationType"/>
      </xs:sequence>
      <xs:attribute name="ruleID" type="URI_Atype" use="required"/>
      <xs:attribute name="formID" type="URI_Atype"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ChangeLogType
Namespace urn:ihe:qrph:sdc:2016
Annotations
Inforamtion about changes to file or part of a
file.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ChangeLogType_ChangedField SDCResources_xsd.tmp#ChangeLogType_ChangedTo SDCResources_xsd.tmp#ChangeLogType_ChangedFrom SDCResources_xsd.tmp#ChangeLogType_ChangeType SDCResources_xsd.tmp#ChangeLogType_Replaces SDCResources_xsd.tmp#ChangeLogType_ChangeDate SDCResources_xsd.tmp#ChangeLogType_ChangeDescription SDCResources_xsd.tmp#ChangeLogType_Editors SDCResources_xsd.tmp#ChangeLogType_ChangeTracking
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children ChangeDate, ChangeDescription, ChangeTracking, ChangeType, ChangedField, ChangedFrom, ChangedTo, Comment, Editors, Extension, Property, Replaces
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ChangeLogType">
  <xs:annotation>
    <xs:documentation>Inforamtion about changes to file or part of a file.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:element name="ChangedField" type="ChangedFieldType">
        </xs:element>
        <xs:element name="ChangedTo" type="DataTypes_SType"/>
        <xs:element name="ChangedFrom" type="DataTypes_SType" minOccurs="1"/>
        <xs:element maxOccurs="unbounded" name="ChangeType" type="string_Stype"/>
        <xs:element name="Replaces" maxOccurs="1" minOccurs="0" type="ReplacedIDsType">
          <xs:annotation>
            <xs:documentation>The retired/deprecated item that is being replaced.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="ChangeDate" type="dateTime_Stype">
        </xs:element>
        <xs:element name="ChangeDescription" type="string_Stype" minOccurs="0"/>
        <xs:element name="Editors" minOccurs="0" type="ContactsType">
        </xs:element>
        <xs:element minOccurs="0" name="ChangeTracking" type="ChangeTrackingType">
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ChangedFieldType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ItemTarget_TargetItemID SDCResources_xsd.tmp#ItemTarget_TargetItemName SDCResources_xsd.tmp#ItemTarget_TargetItemXPath SDCResources_xsd.tmp#ItemTarget
Type extension of ExtensionBaseType
Type hierarchy
Used by
Model
Children Comment, Extension, Property, TargetItemID, TargetItemName, TargetItemXPath
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ChangedFieldType">
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:group ref="ItemTarget"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type TargetItemIDType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#anyURI_Stype_val SDCDataTypes_xsd.tmp#anyURI_Stype SDCResources_xsd.tmp#TargetItemIDType_targetItemText SDCResources_xsd.tmp#TargetItemIDType_targetProperty
Type extension of anyURI_Stype
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
targetProperty xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:anyURI optional
Source
<xs:complexType name="TargetItemIDType">
  <xs:complexContent>
    <xs:extension base="anyURI_Stype">
      <xs:attribute name="targetItemText" type="xs:string">
        <xs:annotation>
          <xs:documentation>Displayed text on the targetted item.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="targetProperty" type="xs:string"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type TargetItemNameType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#TargetItemNameType_val SDCResources_xsd.tmp#TargetItemNameType_targetItemText SDCResources_xsd.tmp#TargetItemNameType_targetProperty
Type extension of BaseType
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
targetProperty xs:string optional
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:NCName optional
Source
<xs:complexType name="TargetItemNameType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:attribute name="val" type="xs:NCName">
      </xs:attribute>
      <xs:attribute name="targetItemText" type="xs:string">
        <xs:annotation>
          <xs:documentation>Displayed text on the targetted item.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="targetProperty" type="xs:string"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type TargetItemXPathType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#TargetItemXPathType_targetItemText
Type extension of string_Stype
Type hierarchy
Used by
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
targetItemText xs:string optional
Displayed text on the targetted item.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:complexType name="TargetItemXPathType">
  <xs:complexContent>
    <xs:extension base="string_Stype">
      <xs:attribute name="targetItemText" type="xs:string">
        <xs:annotation>
          <xs:documentation>Displayed text on the targetted item.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ReplacedIDsType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ReplacedIDsType_ReplacedID
Type extension of BaseType
Type hierarchy
Used by
Model
Children ReplacedID
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ReplacedIDsType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:sequence maxOccurs="unbounded">
        <xs:element name="ReplacedID" type="anyURI_Stype">
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type ChangeTrackingType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ChangeTrackingType_ChangeTrackingID
Type extension of BaseType
Type hierarchy
Used by
Model
Children ChangeTrackingID
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ChangeTrackingType">
  <xs:complexContent>
    <xs:extension base="BaseType">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" name="ChangeTrackingID" type="string_Stype"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type AcceptabilityType
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCDataTypes_xsd.tmp#string_Stype_val SDCDataTypes_xsd.tmp#string_Stype SDCResources_xsd.tmp#AcceptabilityType_val
Type restriction of string_Stype
Type hierarchy
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val Acceptability_StypeEnum required
Source
<xs:complexType name="AcceptabilityType">
  <xs:complexContent>
    <xs:restriction base="string_Stype">
      <xs:attribute name="val" type="Acceptability_StypeEnum" use="required"/>
    </xs:restriction>
  </xs:complexContent>
</xs:complexType>
Simple Type Acceptability_StypeEnum
Namespace urn:ihe:qrph:sdc:2016
Annotations
Enumeration for specifying the level of aceptability for SDC form items.
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration preferred
enumeration admitted
ISO 10241-1:2011 defines "admitted term" as: synonymous term (3.4.1.1.2) for a preferred term (3.4.1.3.1), but not rated as a preferred term by a standardizing body
enumeration deprecated
enumeration obsolete
enumeration superseded
Used by
Source
<xs:simpleType name="Acceptability_StypeEnum">
  <xs:annotation>
    <xs:documentation>Enumeration for specifying the level of aceptability for SDC form items.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:enumeration value="preferred"/>
    <xs:enumeration value="admitted">
      <xs:annotation>
        <xs:documentation>ISO 10241-1:2011 defines "admitted term" as: synonymous term (3.4.1.1.2) for a preferred term (3.4.1.3.1), but not rated as a preferred term by a standardizing body</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <xs:enumeration value="deprecated"/>
    <xs:enumeration value="obsolete"/>
    <xs:enumeration value="superseded"/>
  </xs:restriction>
</xs:simpleType>
Complex Type ChangeType
Namespace urn:ihe:qrph:sdc:2016
Annotations
A structure to describe a single change in an XML document
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#ItemTarget_TargetItemID SDCResources_xsd.tmp#ItemTarget_TargetItemName SDCResources_xsd.tmp#ItemTarget_TargetItemXPath SDCResources_xsd.tmp#ItemTarget SDCResources_xsd.tmp#ChangeType_NewValue
Type extension of ExtensionBaseType
Type hierarchy
Model
Children Comment, Extension, NewValue, Property, TargetItemID, TargetItemName, TargetItemXPath
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="ChangeType">
  <xs:annotation>
    <xs:documentation>A structure to describe a single change in an XML document</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:sequence>
        <xs:group ref="ItemTarget"/>
        <xs:element name="NewValue" type="DataTypes_SType">
          <xs:annotation>
            <xs:documentation>The new value that the targeted item's content is set to.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type PropertyType1
Namespace urn:ihe:qrph:sdc:2016
Annotations
MOVED: From SDCFormDesign
CHANGED:
Property is any type of data that is associated with any form item (e.g., section, question, list item) in any context.  The Property context is specified by the @type attribute.  Examples of @type values may include:
-alternate language representations, e.g., 'spanish'
-'instruction'
-'tooltip' 
-'help' for a pop-up help box
-'outlining' (such as question numbering)

The @type enumerations must be defined and documented for the particular use case, and are currently out of scope in this schema definition.  Multiple type tokens for a single element are supported.

RENAMED:  'OtherText' to 'Property' 9/14/2016
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypes_SType_anyType SDCResources_xsd.tmp#DataTypes_SType_anyURI SDCResources_xsd.tmp#DataTypes_SType_base64Binary SDCResources_xsd.tmp#DataTypes_SType_boolean SDCResources_xsd.tmp#DataTypes_SType_duration SDCResources_xsd.tmp#DataTypes_SType_byte SDCResources_xsd.tmp#DataTypes_SType_date SDCResources_xsd.tmp#DataTypes_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypes_SType_decimal SDCResources_xsd.tmp#DataTypes_SType_dateTime SDCResources_xsd.tmp#DataTypes_SType_double SDCResources_xsd.tmp#DataTypes_SType_float SDCResources_xsd.tmp#DataTypes_SType_gDay SDCResources_xsd.tmp#DataTypes_SType_gMonth SDCResources_xsd.tmp#DataTypes_SType_gMonthDay SDCResources_xsd.tmp#DataTypes_SType_gYear SDCResources_xsd.tmp#DataTypes_SType_gYearMonth SDCResources_xsd.tmp#DataTypes_SType_hexBinary SDCResources_xsd.tmp#DataTypes_SType_HTML SDCResources_xsd.tmp#DataTypes_SType_int SDCResources_xsd.tmp#DataTypes_SType_integer SDCResources_xsd.tmp#DataTypes_SType_long SDCResources_xsd.tmp#DataTypes_SType_negativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypes_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypes_SType_positiveInteger SDCResources_xsd.tmp#DataTypes_SType_short SDCResources_xsd.tmp#DataTypes_SType_string SDCResources_xsd.tmp#DataTypes_SType_time SDCResources_xsd.tmp#DataTypes_SType_unsignedByte SDCResources_xsd.tmp#DataTypes_SType_unsignedInt SDCResources_xsd.tmp#DataTypes_SType_unsignedLong SDCResources_xsd.tmp#DataTypes_SType_unsignedShort SDCResources_xsd.tmp#DataTypes_SType_XML SDCResources_xsd.tmp#DataTypes_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypes_SType SDCResources_xsd.tmp#PropertyType1_propName SDCResources_xsd.tmp#PropertyType1_propClass SDCResources_xsd.tmp#PropertyType1_val
Type extension of DataTypes_SType
Type hierarchy
Model
Children Comment, Extension, HTML, Property, XML, anyType, anyURI, base64Binary, boolean, byte, date, dateTime, dateTimeStamp, decimal, double, duration, float, gDay, gMonth, gMonthDay, gYear, gYearMonth, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, string, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
propClass xs:NMTOKENS optional
NEW
propName xs:NMTOKEN required
NEW
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
val xs:string optional
Source
<xs:complexType name="PropertyType1">
  <xs:annotation>
    <xs:documentation>MOVED: From SDCFormDesign CHANGED: Property is any type of data that is associated with any form item (e.g., section, question, list item) in any context. The Property context is specified by the @type attribute. Examples of @type values may include: -alternate language representations, e.g., 'spanish' -'instruction' -'tooltip' -'help' for a pop-up help box -'outlining' (such as question numbering) The @type enumerations must be defined and documented for the particular use case, and are currently out of scope in this schema definition. Multiple type tokens for a single element are supported. RENAMED: 'OtherText' to 'Property' 9/14/2016</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="DataTypes_SType">
      <xs:attribute form="unqualified" name="propName" type="xs:NMTOKEN" use="required">
        <xs:annotation>
          <xs:documentation>NEW</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute form="unqualified" name="propClass" type="xs:NMTOKENS">
        <xs:annotation>
          <xs:documentation>NEW</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="val" type="xs:string" use="optional"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypesNumeric_DEType
Namespace urn:ihe:qrph:sdc:2016
Annotations
NEW:
SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes  and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypesNumeric_DEType_byte SDCResources_xsd.tmp#DataTypesNumeric_DEType_decimal SDCResources_xsd.tmp#DataTypesNumeric_DEType_double SDCResources_xsd.tmp#DataTypesNumeric_DEType_float SDCResources_xsd.tmp#DataTypesNumeric_DEType_hexBinary SDCResources_xsd.tmp#DataTypesNumeric_DEType_int SDCResources_xsd.tmp#DataTypesNumeric_DEType_integer SDCResources_xsd.tmp#DataTypesNumeric_DEType_long SDCResources_xsd.tmp#DataTypesNumeric_DEType_negativeInteger SDCResources_xsd.tmp#DataTypesNumeric_DEType_nonNegativeInteger SDCResources_xsd.tmp#DataTypesNumeric_DEType_nonPositiveInteger SDCResources_xsd.tmp#DataTypesNumeric_DEType_positiveInteger SDCResources_xsd.tmp#DataTypesNumeric_DEType_short SDCResources_xsd.tmp#DataTypesNumeric_DEType_time SDCResources_xsd.tmp#DataTypesNumeric_DEType_unsignedByte SDCResources_xsd.tmp#DataTypesNumeric_DEType_unsignedInt SDCResources_xsd.tmp#DataTypesNumeric_DEType_unsignedLong SDCResources_xsd.tmp#DataTypesNumeric_DEType_unsignedShort SDCResources_xsd.tmp#DataTypesNumeric_DEType_yearMonthDuration
Type extension of ExtensionBaseType
Type hierarchy
Model
Children Comment, Extension, Property, byte, decimal, double, float, hexBinary, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, time, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypesNumeric_DEType">
  <xs:annotation>
    <xs:documentation>NEW: SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="byte" nillable="true" type="byte_DEtype">
        </xs:element>
        <xs:element name="decimal" nillable="true" type="decimal_DEtype">
        </xs:element>
        <xs:element name="double" nillable="true" type="double_DEtype"/>
        <xs:element name="float" nillable="true" type="float_DEtype"/>
        <xs:element name="hexBinary" nillable="true" type="hexBinary_DEtype"/>
        <xs:element name="int" nillable="true" type="int_DEtype">
        </xs:element>
        <xs:element name="integer" nillable="true" type="integer_DEtype">
        </xs:element>
        <xs:element name="long" nillable="true" type="long_DEtype">
        </xs:element>
        <xs:element name="negativeInteger" nillable="true" type="negativeInteger_DEtype"/>
        <xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_DEtype"/>
        <xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_DEtype"/>
        <xs:element name="positiveInteger" nillable="true" type="positiveInteger_DEtype"/>
        <xs:element name="short" nillable="true" type="short_DEtype"/>
        <xs:element name="time" nillable="true" type="time_DEtype">
          <xs:annotation>
            <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="unsignedByte" nillable="true" type="unsignedByte_DEtype"/>
        <xs:element name="unsignedInt" nillable="true" type="unsignedInt_DEtype"/>
        <xs:element name="unsignedLong" nillable="true" type="unsignedLong_DEtype"/>
        <xs:element name="unsignedShort" nillable="true" type="unsignedShort_DEtype"/>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
        </xs:element>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypesNumeric_SType
Namespace urn:ihe:qrph:sdc:2016
Annotations
NEW:
SDC datatypes in Simple (S) format, based mostly on W3C specifications.  Uses baseAttributes and Extension capability to enhance the list of Data Types.        **CHECK for ERRORS and completeness**
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypesNumeric_SType_byte SDCResources_xsd.tmp#DataTypesNumeric_SType_decimal SDCResources_xsd.tmp#DataTypesNumeric_SType_double SDCResources_xsd.tmp#DataTypesNumeric_SType_float SDCResources_xsd.tmp#DataTypesNumeric_SType_int SDCResources_xsd.tmp#DataTypesNumeric_SType_integer SDCResources_xsd.tmp#DataTypesNumeric_SType_long SDCResources_xsd.tmp#DataTypesNumeric_SType_negativeInteger SDCResources_xsd.tmp#DataTypesNumeric_SType_nonNegativeInteger SDCResources_xsd.tmp#DataTypesNumeric_SType_nonPositiveInteger SDCResources_xsd.tmp#DataTypesNumeric_SType_positiveInteger SDCResources_xsd.tmp#DataTypesNumeric_SType_short SDCResources_xsd.tmp#DataTypesNumeric_SType_unsignedByte SDCResources_xsd.tmp#DataTypesNumeric_SType_unsignedInt SDCResources_xsd.tmp#DataTypesNumeric_SType_unsignedLong SDCResources_xsd.tmp#DataTypesNumeric_SType_unsignedShort SDCResources_xsd.tmp#DataTypesNumeric_SType_yearMonthDuration
Type extension of ExtensionBaseType
Type hierarchy
Model
Children Comment, Extension, Property, byte, decimal, double, float, int, integer, long, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger, short, unsignedByte, unsignedInt, unsignedLong, unsignedShort, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypesNumeric_SType">
  <xs:annotation>
    <xs:documentation>NEW: SDC datatypes in Simple (S) format, based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. **CHECK for ERRORS and completeness**</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="byte" nillable="true" type="byte_Stype">
        </xs:element>
        <xs:element name="decimal" nillable="true" type="decimal_Stype">
          <xs:annotation>
            <xs:documentation/>
          </xs:annotation>
        </xs:element>
        <xs:element name="double" nillable="true" type="double_Stype"/>
        <xs:element name="float" nillable="true" type="float_Stype"/>
        <xs:element name="int" nillable="true" type="int_Stype">
        </xs:element>
        <xs:element name="integer" nillable="true" type="integer_Stype">
        </xs:element>
        <xs:element name="long" nillable="true" type="long_Stype"/>
        <xs:element name="negativeInteger" nillable="true" type="negativeInteger_Stype"/>
        <xs:element name="nonNegativeInteger" nillable="true" type="nonNegativeInteger_Stype"/>
        <xs:element name="nonPositiveInteger" nillable="true" type="nonPositiveInteger_Stype"/>
        <xs:element name="positiveInteger" nillable="true" type="positiveInteger_Stype"/>
        <xs:element name="short" nillable="true" type="short_Stype"/>
        <xs:element name="unsignedByte" nillable="true" type="unsignedByte_Stype"/>
        <xs:element name="unsignedInt" nillable="true" type="unsignedInt_Stype"/>
        <xs:element name="unsignedLong" nillable="true" type="unsignedLong_Stype"/>
        <xs:element name="unsignedShort" nillable="true" type="unsignedShort_Stype"/>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypesDateTime_DEType
Namespace urn:ihe:qrph:sdc:2016
Annotations
NEW:
SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes  and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypesDateTime_DEType_dateTime SDCResources_xsd.tmp#DataTypesDateTime_DEType_duration SDCResources_xsd.tmp#DataTypesDateTime_DEType_gMonthDay SDCResources_xsd.tmp#DataTypesDateTime_DEType_gYear SDCResources_xsd.tmp#DataTypesDateTime_DEType_gYearMonth SDCResources_xsd.tmp#DataTypesDateTime_DEType_time SDCResources_xsd.tmp#DataTypesDateTime_DEType_yearMonthDuration
Type extension of ExtensionBaseType
Type hierarchy
Model
Children Comment, Extension, Property, dateTime, duration, gMonthDay, gYear, gYearMonth, time, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypesDateTime_DEType">
  <xs:annotation>
    <xs:documentation>NEW: SDC datatypes for Data Entry (DE), based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. Includes additonal metadata to specify data input restrictions for data entry forms, and to aid in validation of IHE RFD SubmitForm responses in XML instance documents.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="dateTime" nillable="true" type="dateTimeStamp_DEtype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="duration" nillable="true" type="duration_DEtype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gMonthDay" nillable="true" type="gMonthDay_DEtype"/>
        <xs:element name="gYear" nillable="true" type="gYear_DEtype"/>
        <xs:element name="gYearMonth" nillable="true" type="gMonth_DEtype"/>
        <xs:element name="time" nillable="true" type="time_DEtype">
          <xs:annotation>
            <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_DEtype">
        </xs:element>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Complex Type DataTypesDateTime_SType
Namespace urn:ihe:qrph:sdc:2016
Annotations
NEW:
SDC datatypes in Simple (S) format, based mostly on W3C specifications.  Uses baseAttributes and Extension capability to enhance the list of Data Types.        **CHECK for ERRORS and completeness**
Diagram
Diagram SDCBase_xsd.tmp#baseAttributes SDCBase_xsd.tmp#BaseType SDCResources_xsd.tmp#ExtensionBaseType_Comment SDCResources_xsd.tmp#ExtensionBaseType_Extension SDCResources_xsd.tmp#ExtensionBaseType_Property SDCResources_xsd.tmp#ExtensionBaseType SDCResources_xsd.tmp#DataTypesDateTime_SType_duration SDCResources_xsd.tmp#DataTypesDateTime_SType_date SDCResources_xsd.tmp#DataTypesDateTime_SType_dateTimeStamp SDCResources_xsd.tmp#DataTypesDateTime_SType_dateTime SDCResources_xsd.tmp#DataTypesDateTime_SType_gDay SDCResources_xsd.tmp#DataTypesDateTime_SType_gMonth SDCResources_xsd.tmp#DataTypesDateTime_SType_gMonthDay SDCResources_xsd.tmp#DataTypesDateTime_SType_gYear SDCResources_xsd.tmp#DataTypesDateTime_SType_gYearMonth SDCResources_xsd.tmp#DataTypesDateTime_SType_time SDCResources_xsd.tmp#DataTypesDateTime_SType_yearMonthDuration SDCResources_xsd.tmp#DataTypesDateTime_SType_List000
Type extension of ExtensionBaseType
Type hierarchy
Model
Children Comment, Extension, List000, Property, date, dateTime, dateTimeStamp, duration, gDay, gMonth, gMonthDay, gYear, gYearMonth, time, yearMonthDuration
Attributes
QName Type Use Annotation
name xs:ID optional
Developer assigned identifier, similar to a unique control/object
name, used to provide the ability for programmatic manipulation of an
element.
order restriction of xs:decimal optional
@order allows the form template developer to define a sequential
order for elements in a template. This serves the purpose of providing a
definitive/original order to sections, questions, answer choices, etc., when
required for display purposes. This is important when the original XML ordering
may become disrupted due to the use of an implementation technology that does
not natively support ordering (e.g., object collections), and it can also
provide a check on the proper importing of the XML tree during
implementation.
styleClass xs:NMTOKENS optional
Developer assigned class name for display styling, generally for
use with an external style sheet.
type xs:NMTOKENS optional
The @type attribute can contain custom metadata "tokens" for the
element, chosen from a standardized list of terms. Tokens are short alphanumeric
text strings, defined by the W3C Schema NMTOKEN specification, that are defined
in an Implementation Guide. The type xsd:NMTOKEN represents a single string
token. NMTOKEN values may consist of letters, digits, periods ( . ), hyphens ( -
), underscores ( _ ), and colons ( : ). They may start with any of these
characters. (www.datypic.com/sc/xsd/t-xsd_NMTOKEN.html) @type tokens may be
specific for one or more kinds of SDC elements. Multiple tokens in the type
attribute should be separated by whitespace. Type tokens may be used to specify
special handling by an application, and are usually used to define form display
constraints, but may include other custom metadata as well. Style metadata
should generally be handled with @styleClass rather than @type. @type token
examples include: tooltip, statusLineText, alignTopLeft, align:bottom,
_pageBreak-after, etc. @type metadata should generally not affect the
information content of a form.
Source
<xs:complexType name="DataTypesDateTime_SType">
  <xs:annotation>
    <xs:documentation>NEW: SDC datatypes in Simple (S) format, based mostly on W3C specifications. Uses baseAttributes and Extension capability to enhance the list of Data Types. **CHECK for ERRORS and completeness**</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="ExtensionBaseType">
      <xs:choice>
        <xs:element name="duration" nillable="true" type="duration_Stype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">Duration Data Type The duration data type is used to specify a time interval. The time interval is specified in the following form: "PnYnMnDTnHnMnS" where: P indicates the period (required) nY indicates the number of years nM indicates the number of months nD indicates the number of days T indicates the start of a time section (required if you are going to specify hours, minutes, or seconds) nH indicates the number of hours nM indicates the number of minutes nS indicates the number of seconds An element in your document might look like this: P5Y The example above indicates a period of five years. Or it might look like this: P5Y2M10D. The example above indicates a period of five years, two months, and 10 days. Or it might look like this: P5Y2M10DT15H. The example above indicates a period of five years, two months, 10 days, and 15 hours. Or it might look like this: PT15H.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="date" nillable="true" type="date_Stype">
          <xs:annotation>
            <xs:documentation>**Does SDC need a list of valid patterns for all date/time types?</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="dateTimeStamp" nillable="true" type="dateTimeStamp_Stype">
          <xs:annotation>
            <xs:documentation>
            </xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="dateTime" nillable="true" type="dateTimeStamp_Stype">
          <xs:annotation>
            <xs:documentation source="http://www.w3schools.com/schema/schema_dtypes_date.asp">DateTime Data Type The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Time Zones To specify a time zone, you can either enter a time in UTC time by adding a "Z" behind the time - like this: 09:30:10Z or you can specify an offset from the UTC time by adding a positive or negative time behind the time - like this: 09:30:10-06:00 or 09:30:10+06:00.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gDay" nillable="true" type="gDay_Stype"/>
        <xs:element name="gMonth" nillable="true" type="gMonth_Stype"/>
        <xs:element name="gMonthDay" nillable="true" type="gMonthDay_Stype"/>
        <xs:element name="gYear" nillable="true" type="gYear_Stype"/>
        <xs:element name="gYearMonth" nillable="true" type="gMonth_Stype"/>
        <xs:element name="time" nillable="true" type="time_Stype">
          <xs:annotation>
            <xs:documentation>**possibly "HH:MM:SS:ms am/pm 12/24"</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="yearMonthDuration" nillable="true" type="yearMonthDuration_Stype"/>
        <xs:element name="List000"/>
      </xs:choice>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
Attribute PropertyType / @propName
Namespace No namespace
Annotations
NEW
Type xs:NMTOKEN
Properties
use required
Used by
Complex Type PropertyType
Source
<xs:attribute form="unqualified" name="propName" type="xs:NMTOKEN" use="required">
  <xs:annotation>
    <xs:documentation>NEW</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PropertyType / @propClass
Namespace No namespace
Annotations
NEW
Type xs:NMTOKENS
Properties
content simple
Used by
Complex Type PropertyType
Source
<xs:attribute form="unqualified" name="propClass" type="xs:NMTOKENS">
  <xs:annotation>
    <xs:documentation>NEW</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PropertyType / @val
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Complex Type PropertyType
Source
<xs:attribute name="val" type="xs:string" use="optional"/>
Attribute IDAttributes / @ID
Namespace No namespace
Annotations
A unique identifier for critical types in FormDesign.
TODO: Needs Schematron to calidate uniqueness in each form.
Type URI_Atype
Properties
use required
Facets
minLength 1
Used by
Attribute Group IDAttributes
Source
<xs:attribute name="ID" type="URI_Atype" use="required">
  <xs:annotation>
    <xs:documentation>A unique identifier for critical types in FormDesign. TODO: Needs Schematron to calidate uniqueness in each form.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute IDAttributes / @baseURI
Namespace No namespace
Annotations
If the ID does not use the default base URI (namespace), then the local baseURI goes here. Note that all IDs must be unique within a form, even if they do not have the same baseURI. 

Ideally, the baseURI + ID should combine to form a *globally* unique identifier, that uniquely identifies an item in a particular form.  The same baseURI and ID may be reused in derived or versioned forms, as long as the context stays the same, and any affected data elements remain unchanged in context and semantics.  Following this approach is likely to simplify analytics based on form content.
Type URI_Atype
Properties
content simple
Facets
minLength 1
Used by
Attribute Group IDAttributes
Source
<xs:attribute name="baseURI" type="URI_Atype">
  <xs:annotation>
    <xs:documentation>If the ID does not use the default base URI (namespace), then the local baseURI goes here. Note that all IDs must be unique within a form, even if they do not have the same baseURI. Ideally, the baseURI + ID should combine to form a *globally* unique identifier, that uniquely identifies an item in a particular form. The same baseURI and ID may be reused in derived or versioned forms, as long as the context stays the same, and any affected data elements remain unchanged in context and semantics. Following this approach is likely to simplify analytics based on form content.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute ItemNameType / @itemName
Namespace No namespace
Annotations
The @name attribute of the referenced element.
Type xs:NCName
Properties
use required
Used by
Complex Type ItemNameType
Source
<xs:attribute name="itemName" type="xs:NCName" use="required">
  <xs:annotation>
    <xs:documentation>The @name attribute of the referenced element.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute RichTextType / @val
Namespace No namespace
Type xs:string
Properties
use required
Used by
Complex Type RichTextType
Source
<xs:attribute name="val" type="xs:string" use="required"/>
Attribute CodeMatchType / @codeMatchEnum
Namespace No namespace
Annotations
The degree of match between the coded item and the assigned code.
Type restriction of xs:string
Properties
default Exact Code Match
Facets
enumeration Exact Code Match
enumeration Close Code Match
enumeration Code Broader Than Item
enumeration Code Narrower Than Item
enumeration Item Implements Data Element Exactly
enumeration Item Derived From Data Element
enumeration Item Related To Data Element
Used by
Complex Type CodeMatchType
Source
<xs:attribute name="codeMatchEnum" default="Exact Code Match">
  <xs:annotation>
    <xs:documentation>The degree of match between the coded item and the assigned code.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Exact Code Match"/>
      <xs:enumeration value="Close Code Match"/>
      <xs:enumeration value="Code Broader Than Item"/>
      <xs:enumeration value="Code Narrower Than Item"/>
      <xs:enumeration value="Item Implements Data Element Exactly"/>
      <xs:enumeration value="Item Derived From Data Element"/>
      <xs:enumeration value="Item Related To Data Element"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute UnitsType / @unitSystem
Namespace No namespace
Type xs:string
Properties
use optional
default UCUM
Used by
Complex Type UnitsType
Source
<xs:attribute default="UCUM" name="unitSystem" type="xs:string" use="optional"/>
Attribute HashType / @hashAlgorithm
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type HashType
Source
<xs:attribute name="hashAlgorithm" type="xs:string"/>
Attribute BlobType / @mimeType
Namespace No namespace
Annotations
TBD: Must be a valid MIME type - needs enumeration
Type xs:string
Properties
use required
Used by
Complex Type BlobType
Source
<xs:attribute name="mimeType" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>TBD: Must be a valid MIME type - needs enumeration</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute BlobType / @fileExtension
Namespace No namespace
Annotations
Use a common file extension (e.g., docx) if there is no @MIME_Type available
Type xs:string
Properties
use optional
Used by
Complex Type BlobType
Source
<xs:attribute name="fileExtension" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>Use a common file extension (e.g., docx) if there is no @MIME_Type available</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute EmailAddressType / @val
Namespace No namespace
Type EmailAddress_Stype
Properties
use required
Facets
pattern [a-zA-Z0-9_\-\.\+-]+@[a-zA-Z0-9\-]+\.[a-zA-Z0-9_\-\.]+
Used by
Complex Type EmailAddressType
Source
<xs:attribute name="val" use="required" type="EmailAddress_Stype">
</xs:attribute>
Attribute CountryCodeType / @val
Namespace No namespace
Type CountryCode_Stype
Properties
use required
Facets
maxInclusive 99
Used by
Complex Type CountryCodeType
Source
<xs:attribute name="val" use="required" type="CountryCode_Stype">
</xs:attribute>
Attribute AreaCodeType / @val
Namespace No namespace
Type AreaCode_Stype
Properties
use optional
Facets
maxInclusive 999
Used by
Complex Type AreaCodeType
Source
<xs:attribute name="val" use="optional" type="AreaCode_Stype">
</xs:attribute>
Attribute PhoneNumberType / @val
Namespace No namespace
Type PhoneNumber_Stype
Properties
use required
Facets
pattern \+?\(?\d{2,4}\)?[\d\s-]{3,}
Used by
Complex Type PhoneNumberType
Source
<xs:attribute name="val" use="required" type="PhoneNumber_Stype">
</xs:attribute>
Attribute IdentifierType / @system
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type IdentifierType
Source
<xs:attribute name="system" type="xs:string"/>
Attribute IdentifierType / @val
Namespace No namespace
Type xs:string
Properties
use required
Used by
Complex Type IdentifierType
Source
<xs:attribute name="val" type="xs:string" use="required"/>
Attribute ItemNameAttributeType / @attributeName
Namespace No namespace
Type xs:NCName
Properties
default val
Used by
Complex Type ItemNameAttributeType
Source
<xs:attribute default="val" name="attributeName" type="xs:NCName"/>
Attribute FileHashType / @hashType
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type FileHashType
Source
<xs:attribute name="hashType" type="xs:string"/>
Attribute LanguageCode.ISO.639.3_Type / @val
Namespace No namespace
Type LanguageCode.ISO.639.3_StypeEnum
Properties
use required
Facets
enumeration eng
enumeration esp
enumeration fra
Used by
Source
<xs:attribute name="val" use="required" type="LanguageCode.ISO.639.3_StypeEnum">
</xs:attribute>
Attribute SubmissionRuleType / @formID
Namespace No namespace
Type URI_Atype
Properties
content simple
Facets
minLength 1
Used by
Complex Type SubmissionRuleType
Source
<xs:attribute name="formID" type="URI_Atype"/>
Attribute SubmissionRuleType / @ruleID
Namespace No namespace
Type URI_Atype
Properties
use required
Facets
minLength 1
Used by
Complex Type SubmissionRuleType
Source
<xs:attribute name="ruleID" type="URI_Atype" use="required"/>
Attribute ComplianceRuleType / @ruleID
Namespace No namespace
Type URI_Atype
Properties
use required
Facets
minLength 1
Used by
Complex Type ComplianceRuleType
Source
<xs:attribute name="ruleID" type="URI_Atype" use="required"/>
Attribute ComplianceRuleType / @formID
Namespace No namespace
Type URI_Atype
Properties
content simple
Facets
minLength 1
Used by
Complex Type ComplianceRuleType
Source
<xs:attribute name="formID" type="URI_Atype"/>
Attribute TargetItemIDType / @targetItemText
Namespace No namespace
Annotations
Displayed text on the targetted item.
Type xs:string
Properties
content simple
Used by
Complex Type TargetItemIDType
Source
<xs:attribute name="targetItemText" type="xs:string">
  <xs:annotation>
    <xs:documentation>Displayed text on the targetted item.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute TargetItemIDType / @targetProperty
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type TargetItemIDType
Source
<xs:attribute name="targetProperty" type="xs:string"/>
Attribute TargetItemNameType / @val
Namespace No namespace
Type xs:NCName
Properties
content simple
Used by
Complex Type TargetItemNameType
Source
<xs:attribute name="val" type="xs:NCName">
</xs:attribute>
Attribute TargetItemNameType / @targetItemText
Namespace No namespace
Annotations
Displayed text on the targetted item.
Type xs:string
Properties
content simple
Used by
Complex Type TargetItemNameType
Source
<xs:attribute name="targetItemText" type="xs:string">
  <xs:annotation>
    <xs:documentation>Displayed text on the targetted item.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute TargetItemNameType / @targetProperty
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type TargetItemNameType
Source
<xs:attribute name="targetProperty" type="xs:string"/>
Attribute TargetItemXPathType / @targetItemText
Namespace No namespace
Annotations
Displayed text on the targetted item.
Type xs:string
Properties
content simple
Used by
Complex Type TargetItemXPathType
Source
<xs:attribute name="targetItemText" type="xs:string">
  <xs:annotation>
    <xs:documentation>Displayed text on the targetted item.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute versionAttributes / @fullVersion
Namespace No namespace
Type xs:string
Properties
use required
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="fullVersion" type="xs:string" use="required"/>
Attribute versionAttributes / @versionRegExPattern
Namespace No namespace
Annotations
Regular Expression that determines the format of the Full Version
Type xs:string
Properties
use required
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionRegExPattern" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>Regular Expression that determines the format of the Full Version</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute versionAttributes / @versionLevel.1
Namespace No namespace
Annotations
Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.
Type xs:string
Properties
use optional
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionLevel.1" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute versionAttributes / @versionLevel.2
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionLevel.2" type="xs:string" use="optional"/>
Attribute versionAttributes / @versionLevel.3
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionLevel.3" type="xs:string" use="optional"/>
Attribute versionAttributes / @versionLevel.4
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionLevel.4" type="xs:string" use="optional"/>
Attribute versionAttributes / @versionLevel.5
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Attribute Group versionAttributes
Source
<xs:attribute name="versionLevel.5" type="xs:string" use="optional"/>
Attribute AcceptabilityType / @val
Namespace No namespace
Type Acceptability_StypeEnum
Properties
use required
Facets
enumeration preferred
enumeration admitted
ISO 10241-1:2011 defines "admitted term" as: synonymous term (3.4.1.1.2) for a preferred term (3.4.1.3.1), but not rated as a preferred term by a standardizing body
enumeration deprecated
enumeration obsolete
enumeration superseded
Used by
Complex Type AcceptabilityType
Source
<xs:attribute name="val" type="Acceptability_StypeEnum" use="required"/>
Attribute templateAttributes / @templateID
Namespace No namespace
Annotations
Globally unique identifier for this template
Type restriction of URI_Atype
Type hierarchy
Properties
use required
Facets
minLength 1
Used by
Attribute Group templateAttributes
Source
<xs:attribute name="templateID" use="required">
  <xs:annotation>
    <xs:documentation>Globally unique identifier for this template</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="URI_Atype">
      <xs:minLength value="1"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute templateAttributes / @targetTemplateID
Namespace No namespace
Annotations
Globally unique identifier for the template targeted by this template
Type restriction of URI_Atype
Type hierarchy
Properties
use required
Facets
minLength 1
Used by
Attribute Group templateAttributes
Source
<xs:attribute name="targetTemplateID" use="required">
  <xs:annotation>
    <xs:documentation>Globally unique identifier for the template targeted by this template</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="URI_Atype">
      <xs:minLength value="1"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Attribute PropertyType1 / @propName
Namespace No namespace
Annotations
NEW
Type xs:NMTOKEN
Properties
use required
Used by
Complex Type PropertyType1
Source
<xs:attribute form="unqualified" name="propName" type="xs:NMTOKEN" use="required">
  <xs:annotation>
    <xs:documentation>NEW</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PropertyType1 / @propClass
Namespace No namespace
Annotations
NEW
Type xs:NMTOKENS
Properties
content simple
Used by
Complex Type PropertyType1
Source
<xs:attribute form="unqualified" name="propClass" type="xs:NMTOKENS">
  <xs:annotation>
    <xs:documentation>NEW</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute PropertyType1 / @val
Namespace No namespace
Type xs:string
Properties
use optional
Used by
Complex Type PropertyType1
Source
<xs:attribute name="val" type="xs:string" use="optional"/>
Element Group ItemTarget
Namespace urn:ihe:qrph:sdc:2016
Annotations
A pointer to an element or attribute in an XML document.
Diagram
Diagram SDCResources_xsd.tmp#ItemTarget_TargetItemID SDCResources_xsd.tmp#ItemTarget_TargetItemName SDCResources_xsd.tmp#ItemTarget_TargetItemXPath
Used by
Complex Types ChangeType, ChangedFieldType
Model
Children TargetItemID, TargetItemName, TargetItemXPath
Source
<xs:group name="ItemTarget">
  <xs:annotation>
    <xs:documentation>A pointer to an element or attribute in an XML document.</xs:documentation>
  </xs:annotation>
  <xs:choice>
    <xs:element name="TargetItemID" type="TargetItemIDType">
      <xs:annotation>
        <xs:documentation>Unique ID of the target item.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="TargetItemName" type="TargetItemNameType">
      <xs:annotation>
        <xs:documentation>@name attribute of target item. (xs:NCName is the base type of xs:ID)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="TargetItemXPath" type="TargetItemXPathType">
      <xs:annotation>
        <xs:documentation>XPath to target item</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:group>
Attribute Group IDAttributes
Namespace urn:ihe:qrph:sdc:2016
Diagram
Diagram SDCResources_xsd.tmp#IDAttributes_ID SDCResources_xsd.tmp#IDAttributes_baseURI
Used by
Attributes
QName Type Use Annotation
ID URI_Atype required
A unique identifier for critical types in FormDesign.
TODO: Needs Schematron to calidate uniqueness in each form.
baseURI URI_Atype optional
If the ID does not use the default base URI (namespace), then the local baseURI goes here. Note that all IDs must be unique within a form, even if they do not have the same baseURI. 

Ideally, the baseURI + ID should combine to form a *globally* unique identifier, that uniquely identifies an item in a particular form.  The same baseURI and ID may be reused in derived or versioned forms, as long as the context stays the same, and any affected data elements remain unchanged in context and semantics.  Following this approach is likely to simplify analytics based on form content.
Source
<xs:attributeGroup name="IDAttributes">
  <xs:attribute name="ID" type="URI_Atype" use="required">
    <xs:annotation>
      <xs:documentation>A unique identifier for critical types in FormDesign. TODO: Needs Schematron to calidate uniqueness in each form.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="baseURI" type="URI_Atype">
    <xs:annotation>
      <xs:documentation>If the ID does not use the default base URI (namespace), then the local baseURI goes here. Note that all IDs must be unique within a form, even if they do not have the same baseURI. Ideally, the baseURI + ID should combine to form a *globally* unique identifier, that uniquely identifies an item in a particular form. The same baseURI and ID may be reused in derived or versioned forms, as long as the context stays the same, and any affected data elements remain unchanged in context and semantics. Following this approach is likely to simplify analytics based on form content.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>
Attribute Group versionAttributes
Namespace urn:ihe:qrph:sdc:2016
Annotations
A global attribute group for recording file version metadata.
Diagram
Diagram SDCResources_xsd.tmp#versionAttributes_fullVersion SDCResources_xsd.tmp#versionAttributes_versionRegExPattern SDCResources_xsd.tmp#versionAttributes_versionLevel.1 SDCResources_xsd.tmp#versionAttributes_versionLevel.2 SDCResources_xsd.tmp#versionAttributes_versionLevel.3 SDCResources_xsd.tmp#versionAttributes_versionLevel.4 SDCResources_xsd.tmp#versionAttributes_versionLevel.5
Used by
Complex Type VersionType
Attributes
QName Type Use Annotation
fullVersion xs:string required
versionLevel.1 xs:string optional
Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.
versionLevel.2 xs:string optional
versionLevel.3 xs:string optional
versionLevel.4 xs:string optional
versionLevel.5 xs:string optional
versionRegExPattern xs:string required
Regular Expression that determines the format of the Full Version
Source
<xs:attributeGroup name="versionAttributes">
  <xs:annotation>
    <xs:documentation>A global attribute group for recording file version metadata.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="fullVersion" type="xs:string" use="required"/>
  <xs:attribute name="versionRegExPattern" type="xs:string" use="required">
    <xs:annotation>
      <xs:documentation>Regular Expression that determines the format of the Full Version</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="versionLevel.1" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>Provides support for a one to five part "semantic" versioning system, such as 111.222.333.444.555, in which each section separated by periods indicates a specific type of change.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="versionLevel.2" type="xs:string" use="optional"/>
  <xs:attribute name="versionLevel.3" type="xs:string" use="optional"/>
  <xs:attribute name="versionLevel.4" type="xs:string" use="optional"/>
  <xs:attribute name="versionLevel.5" type="xs:string" use="optional"/>
</xs:attributeGroup>
Attribute Group templateAttributes
Namespace urn:ihe:qrph:sdc:2016
Annotations
A standard set of attributes to identify the current template, as well as a target template that the current template is dependent upon.
Diagram
Diagram SDCResources_xsd.tmp#templateAttributes_templateID SDCResources_xsd.tmp#templateAttributes_targetTemplateID
Attributes
QName Type Use Annotation
targetTemplateID restriction of URI_Atype required
Globally unique identifier for the template targeted by this template
templateID restriction of URI_Atype required
Globally unique identifier for this template
Source
<xs:attributeGroup name="templateAttributes">
  <xs:annotation>
    <xs:documentation>A standard set of attributes to identify the current template, as well as a target template that the current template is dependent upon.</xs:documentation>
  </xs:annotation>
  <xs:attribute name="templateID" use="required">
    <xs:annotation>
      <xs:documentation>Globally unique identifier for this template</xs:documentation>
    </xs:annotation>
    <xs:simpleType>
      <xs:restriction base="URI_Atype">
        <xs:minLength value="1"/>
      </xs:restriction>
    </xs:simpleType>
  </xs:attribute>
  <xs:attribute name="targetTemplateID" use="required">
    <xs:annotation>
      <xs:documentation>Globally unique identifier for the template targeted by this template</xs:documentation>
    </xs:annotation>
    <xs:simpleType>
      <xs:restriction base="URI_Atype">
        <xs:minLength value="1"/>
      </xs:restriction>
    </xs:simpleType>
  </xs:attribute>
</xs:attributeGroup>